User equipment, base station and method

ABSTRACT

A user equipment (UE) is described. The UE may comprise high-layer processing circuitry configured to acquire one or more RRC parameters each indicating an additional physical cell ID. The UE may also comprise transmission circuitry configured to transmit a PUSCH in multiple slots. The multiple slots may be determined by using either an available slot counting method or a physical slot counting method. Whether the available slot counting method or the physical slot counting method is used may depend on whether the number of the RRC parameters exceed a pre-determined number or not.

TECHNICAL FIELD

The present invention relates to a user equipment, a base station and amethod.

BACKGROUND

In the 3rd Generation Partnership Project (3GPP), a radio access methodand a radio network for cellular mobile communications (hereinafter,referred to as Long Term Evolution, or Evolved Universal TerrestrialRadio Access) have been studied. In LTE (Long Term Evolution), a basestation device is also referred to as an evolved NodeB (eNodeB), and aterminal device is also referred to as a User Equipment (UE). LTE is acellular communication system in which multiple areas are deployed in acellular structure, with each of the multiple areas being covered by abase station device. A single base station device may manage multiplecells. Evolved Universal Terrestrial Radio Access is also referred asE-UTRA.

In the 3GPP, the next generation standard (New Radio: NR) has beenstudied in order to make a proposal to theInternational-Mobile-Telecommunication-2020 (IMT-2020) which is astandard for the next generation mobile communication system defined bythe International Telecommunications Union (ITU). NR has been expectedto satisfy a requirement considering three scenarios of enhanced MobileBroadBand (eMBB), massive Machine Type Communication (mMTC), and UltraReliable and Low Latency Communication (URLLC), in a single technologyframework.

For example, wireless communication devices may communicate with one ormore devices using a communication structure. However, the communicationstructure used may only offer limited flexibility and/or efficiency. Asillustrated by this discussion, systems and methods that improvecommunication flexibility and/or efficiency may be beneficial.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a conceptual diagram of a wireless communication systemaccording to an aspect of the present embodiment;

FIGS. 2A and 2B are examples showing the relationship betweensubcarrier-spacing configuration u, the number of OFDM symbols per slotN^(slot) _(symb), and the CP configuration according to an aspect of thepresent embodiment;

FIG. 3 is a diagram showing an example of a method of configuring aresource grid according to an aspect of the present embodiment;

FIG. 4 is a diagram showing a configuration example of a resource grid3001 according to an aspect of the present embodiment;

FIG. 5 is a schematic block diagram showing a configuration example ofthe base station device 3 according to an aspect of the presentembodiment;

FIG. 6 is a schematic block diagram showing a configuration example ofthe terminal device 1 according to an aspect of the present embodiment;

FIG. 7 is a diagram showing a configuration example of an SS/PBCH blockaccording to an aspect of the present embodiment;

FIG. 8 is a diagram showing an example of the monitoring occasion of thesearch-space-set according to an aspect of the present embodiment;

FIG. 9 is an example of a method for a UE;

FIG. 10 is an example of a method for a base station.

DETAILED DESCRIPTION

A user equipment (UE) is described. The UE may comprise high-layerprocessing circuitry configured to acquire one or more RRC parameterseach indicating an additional physical cell ID. The UE may also comprisetransmission circuitry configured to transmit a PUSCH in multiple slots.The multiple slots may be determined by using either an available slotcounting method or a physical slot counting method. Whether theavailable slot counting method or the physical slot counting method isused may depend on whether the number of the RRC parameters exceed apre-determined number or not.

A base station is described. The base station may comprise high-layerprocessing circuitry configured to send one or more RRC parameters eachindicating an additional physical cell ID. The base station may alsocomprise reception circuitry configured to receive a PUSCH in multipleslots. The multiple slots may be determined by using either an availableslot counting method or a physical slot counting method. Whether theavailable slot counting method or the physical slot counting method isused may depend on whether the number of the RRC parameters exceed apre-determined number or not.

A method for a user equipment (UE) is described. The method may compriseacquiring one or more RRC parameters each indicating an additionalphysical cell ID. The method may also comprise transmitting a PUSCH inmultiple slots. The multiple slots may be determined by using either anavailable slot counting method or a physical slot counting method.Whether the available slot counting method or the physical slot countingmethod is used may depend on whether the number of the RRC parametersexceed a pre-determined number or not.

A method for a base station is described. The method may comprisesending one or more RRC parameters each indicating an additionalphysical cell ID. The method may also comprise receiving a PUSCH inmultiple slots. The multiple slots may be determined by using either anavailable slot counting method or a physical slot counting method.Whether the available slot counting method or the physical slot countingmethod is used may depend on whether the number of the RRC parametersexceed a pre-determined number or not.

‘The available slot-based counting (PUSCH repetition counting) isconfigured’ may be referred to as ‘the slot-based counting (PUSCHrepetition counting) set to enabled is configured’ or ‘the slot-basedcounting (PUSCH repetition counting) is enabled’ or ‘an RRC parameterAvailableSlotCounting is enabled’.

‘The available slot-based counting (PUSCH repetition counting) is notconfigured’ may be referred to as ‘the slot-based counting (PUSCHrepetition counting) set to disabled is configured’ or ‘the slot-basedcounting (PUSCH repetition counting) is disabled’ or ‘an RRC parameterfor indicating the available slot-based counting (PUSCH repetitioncounting) is not configured’ or ‘an RRC parameter AvailableSlotCountingis disabled’.

floor (CX) may be a floor function for real number CX. For example,floor (CX) may be a function that provides the largest integer within arange that does not exceed the real number CX. ceil (DX) may be aceiling function to a real number DX. For example, ceil (DX) may be afunction that provides the smallest integer within the range not lessthan the real number DX. mod (EX, FX) may be a function that providesthe remainder obtained by dividing EX by FX. mod (EX, FX) may be afunction that provides a value which corresponds to the remainder ofdividing EX by FX. It is exp (GX)=e {circumflex over ( )} GX. Here, e isNapier number. (HX){circumflex over ( )} (IX) indicates IX to the powerof HX.

In a wireless communication system according to one aspect of thepresent embodiment, at least OFDM (Orthogonal Frequency DivisionMultiplex) is used. An OFDM symbol is a unit of time domain of the OFDM.The OFDM symbol includes at least one or more subcarriers. An OFDMsymbol is converted to a time-continuous signal in baseband signalgeneration. In downlink, at least CP-OFDM (Cyclic Prefix-OrthogonalFrequency Division Multiplex) is used. In uplink, either CP-OFDM orDFT-s-OFDM (Discrete Fourier Transform-spread-Orthogonal FrequencyDivision Multiplex) is used. DFT-s-OFDM may be given by applyingtransform precoding to CP-OFDM. CP-OFDM is OFDM using CP (CyclicPrefix).

The OFDM symbol may be a designation including a CP added to the OFDMsymbol. That is, an OFDM symbol may be configured to include the OFDMsymbol and a CP added to the OFDM symbol.

FIG. 1 is a conceptual diagram of a wireless communication systemaccording to an aspect of the present embodiment. In FIG. 1 , thewireless communication system includes at least terminal device 1A to 1Cand a base station device 3 (BS #3: Base station #3). Hereinafter, theterminal devices 1A to 1C are also referred to as a terminal device 1(UE #1: User Equipment #1).

The base station device 3 may be configured to include one or moretransmission devices (or transmission points, transmission devices,reception devices, transmission points, reception points). When the basestation device 3 is configured by a plurality of transmission devices,each of the plurality of transmission devices may be arranged at adifferent position.

The base station device 3 may provide one or more serving cells. Aserving cell may be defined as a set of resources used for wirelesscommunication. A serving cell is also referred to as a cell.

A serving cell may be configured to include at least one downlinkcomponent carrier (downlink carrier) and/or one uplink component carrier(uplink carrier). A serving cell may be configured to include at leasttwo or more downlink component carriers and/or two or more uplinkcomponent carriers. A downlink component carrier and an uplink componentcarrier are also referred to as component carriers (carriers).

For example, one resource grid may be provided for one componentcarrier. For example, one resource grid may be provided for onecomponent carrier and a subcarrier-spacing configuration u. Asubcarrier-spacing configuration u is also referred to as numerology. Aresource grid includes N^(size,u) _(grid,x)N^(RB) _(sc) subcarriers. Theresource grid starts from a common resource block with indexN^(start, u) _(grid). The common resource block with the indexN^(start, u) _(grid) is also referred to as a reference point of theresource grid. The resource grid includes N^(subframe, u) _(symb) OFDMsymbols. The subscript x indicates the transmission direction andindicates either downlink or uplink. One resource grid is provided foran antenna port p, a subcarrier-spacing configuration u, and atransmission direction x.

Resource grid is also referred to as carrier.

N^(size,u) _(grid,x) and N^(start,u) _(grid) are given based at least onan RRC parameter (e.g. referred to as RRC parameter CarrierBandwidth).The RRC parameter is used to define one or more SCS (SubCarrier-Spacing)specific carriers. One resource grid corresponds to one SCS specificcarrier. One component carrier may comprise one or more SCS specificcarriers. The SCS specific carrier may be included in a systeminformation block (SIB). For each SCS specific carrier, asubcarrier-spacing configuration u may be provided.

FIGS. 2A and 2B are examples showing the relationship betweensubcarrier-spacing configuration u, the number of OFDM symbols per slotN^(slot) _(symb), and the CP configuration according to an aspect of thepresent embodiment. In FIG. 2A, for example, when the subcarrier-spacingconfiguration u is set to 2 and the CP configuration is set to normal CP(normal cyclic prefix), N^(slot) _(symb)=14, N^(frame,u) _(slot)=40,N^(subframe, u) _(slot)=4. Further, in FIG. 2B, for example, when thesubcarrier-spacing configuration u is set to 2 and the CP configurationis set to an extended CP (extended cyclic prefix), N^(slot) _(symb)=12,N^(frame, u) _(slot)=40, N^(subframe, u) _(slot)=4.

In the wireless communication system according to an aspect of thepresent embodiment, a time unit T_(c) may be used to represent thelength of the time domain. The time unit T_(c) isT_(c)=1/(df_(max)*N_(f)). It is df_(max)=480 kHz. It is N_(f)=4096. Theconstant k is k=df_(max)*N_(f)/(df_(ref)N_(f, ref))=64. df_(ref) is 15kHz. N_(f, ref) is 2048.

Transmission of signals in the downlink and/or transmission of signalsin the uplink may be organized into radio frames (system frames, frames)of length T_(f). It is T_(f)=(df_(max) N_(f)/100)*T_(s)=10 ms. One radioframe is configured to include ten subframes. The subframe length isT_(sf)=(df_(max)N_(f)/1000) T_(s)=1 ms. The number of OFDM symbols persubframe is N^(subframe, u) _(symb)=N^(slot) _(symb)N^(subframe,u)_(slot).

For a subcarrier-spacing configuration u, the number of slots includedin a subframe and indexes may be given. For example, slot index n^(u)_(s) may be given in ascending order with an integer value ranging from0 to N^(subframe,u) _(slot)−1 in a subframe. For subcarrier-spacingconfiguration u, the number of slots included in a radio frame andindexes of slots included in the radio frame may be given. Also, theslot index n^(u) _(s, f) may be given in ascending order with an integervalue ranging from 0 to N^(frame,u) _(slot)−1 in the radio frame.Consecutive N^(slot) _(symb) OFDM symbols may be included in one slot.It is N^(slot) _(symb)=14.

FIG. 3 is a diagram showing an example of a method of configuring aresource grid according to an aspect of the present embodiment. Thehorizontal axis in FIG. 3 indicates frequency domain. FIG. 3 shows aconfiguration example of a resource grid of subcarrier-spacingconfiguration u=u₁ in the component carrier 300 and a configurationexample of a resource grid of subcarrier-spacing configuration u=u₂ in acomponent carrier. One or more subcarrier-spacing configuration may beset for a component carrier. Although it is assumed in FIG. 3 thatu₁=u₂−1, various aspects of this embodiment are not limited to thecondition of u₁=u₂−1.

The component carrier 300 is a band having a predetermined width in thefrequency domain.

Point 3000 is an identifier for identifying a subcarrier. Point 3000 isalso referred to as point A. The common resource block (CRB) set 3100 isa set of common resource blocks for the subcarrier-spacing configurationu₁.

Among the common resource block-set 3100, the common resource blockincluding the point 3000 (the block indicated by the upper rightdiagonal line in FIG. 3 ) is also referred to as a reference point ofthe common resource block-set 3100. The reference point of the commonresource block-set 3100 may be a common resource block with index 0 inthe common resource block-set 3100.

The offset 3011 is an offset from the reference point of the commonresource block-set 3100 to the reference point of the resource grid3001. The offset 3011 is indicated by the number of common resourceblocks which is relative to the subcarrier-spacing configuration u₁. Theresource grid 3001 includes N^(size,u) _(grid1,x) common resource blocksstarting from the reference point of the resource grid 3001.

The offset 3013 is an offset from the reference point of the resourcegrid 3001 to the reference point (N^(start,u) _(BWP,i1)) of the BWP(BandWidth Part) 3003 of the index i1.

Common resource block-set 3200 is a set of common resource blocks withrespect to subcarrier-spacing configuration u₂.

A common resource block including the point 3000 (a block indicated by aupper left diagonal line in FIG. 3 ) in the common resource block-set3200 is also referred to as a reference point of the common resourceblock-set 3200. The reference point of the common resource block-set3200 may be a common resource block with index 0 in the common resourceblock-set 3200.

The offset 3012 is an offset from the reference point of the commonresource block-set 3200 to the reference point of the resource grid3002. The offset 3012 is indicated by the number of common resourceblocks for subcarrier-spacing configuration u=u₂. The resource grid 3002includes N^(size,u) _(grid2,x) common resource blocks starting from thereference point of the resource grid 3002.

The offset 3014 is an offset from the reference point of the resourcegrid 3002 to the reference point (N^(start,u) _(BWP,i2)) of the BWP 3004with index i₂.

FIG. 4 is a diagram showing a configuration example of a resource grid3001 according to an aspect of the present embodiment. In the resourcegrid of FIG. 4 , the horizontal axis indicates OFDM symbol indexl_(sym), and the vertical axis indicates the subcarrier index ksc. Theresource grid 3001 includes N^(size,u) _(grid1,)xN^(RB) _(sc)subcarriers, and includes N^(subframesu) _(symb) OFDM symbols. Aresource specified by the subcarrier index k_(sc) and the OFDM symbolindex l_(sym) in a resource grid is also referred to as a resourceelement (RE).

A resource block (RB) includes N^(RB) _(sc) consecutive subcarriers. Aresource block is a generic name of a common resource block, a physicalresource block (PRB), and a virtual resource block (VRB). It is N^(RB)_(sc)=12.

A resource block unit is a set of resources that corresponds to one OFDMsymbol in one resource block. That is, one resource block unit includes12 resource elements which corresponds to one OFDM symbol in oneresource block.

Common resource blocks for a subcarrier-spacing configuration u areindexed in ascending order from 0 in the frequency domain in a commonresource block-set. The common resource block with index 0 for thesubcarrier-spacing configuration u includes (or collides with, matches)the point 3000. The index n^(u) _(CRB) of the common resource block withrespect to the subcarrier-spacing configuration u satisfies therelationship of n^(u) _(CRB)=ceil (k_(sc)/N^(RB) _(sc)). The subcarrierwith k_(sc)=0 is a subcarrier with the same center frequency as thecenter frequency of the subcarrier which corresponds to the point 3000.

Physical resource blocks for a subcarrier-spacing configuration u areindexed in ascending order from 0 in the frequency domain in a BWP. Theindex n^(u) _(PRB) of the physical resource block with respect to thesubcarrier-spacing configuration u satisfies the relationship of n^(u)_(CRB)=n^(u) _(PRB)+N^(start,u) _(BWP,i). The N^(start,u) _(BWP,i)indicates the reference point of BWP with index i.

A BWP is defined as a subset of common resource blocks included in theresource grid. The BWP includes N^(size,u) _(BWP,i) common resourceblocks starting from the reference points N^(start,u) _(BWP,i). A BWPfor the downlink component carrier is also referred to as a downlinkBWP. A BWP for the uplink component carrier is also referred to as anuplink BWP.

An antenna port is defined such that the channel over which a symbol onthe antenna port is conveyed can be inferred from the channel over whichanother symbol on the same antenna port is conveyed. For example, thechannel may correspond to a physical channel. For example, the symbolsmay correspond to OFDM symbols. For example, the symbols may correspondto resource block units. For example, the symbols may correspond toresource elements.

Two antenna ports are said to be QCL (Quasi Co-Located) if thelarge-scale properties of the channel over which a symbol on one antennaport is conveyed can be inferred from the channel over which a symbol onthe other antenna port is conveyed. The large-scale properties includeone or more of delay spread, Doppler spread, Doppler shift, averagegain, average delay, and spatial Rx parameters.

Carrier aggregation may be communication using a plurality of aggregatedserving cells. Carrier aggregation may be communication using aplurality of aggregated component carriers. Carrier aggregation may becommunication using a plurality of aggregated downlink componentcarriers. Carrier aggregation may be communication using a plurality ofaggregated uplink component carriers.

FIG. 5 is a schematic block diagram showing a configuration example ofthe base station device 3 according to an aspect of the presentembodiment. As shown in FIG. 5 , the base station device 3 includes atleast a part or all of the wireless transmission/reception unit(physical layer processing unit) 30 and the higher-layer processing unit34. The wireless transmission/reception unit 30 includes at least a partor all of the antenna unit 31, the RF unit 32 (Radio Frequency unit 32),and the baseband unit 33. The higher-layer processing unit 34 includesat least a part or all of the medium access control layer processingunit 35 and the radio resource control (RRC) layer processing unit 36.

The wireless transmission/reception unit 30 includes at least a part ofor all of a wireless transmission unit 30 a and a wireless receptionunit 30 b. The configuration of the baseband unit 33 included in thewireless transmission unit 30 a and the configuration of the basebandunit 33 included in the wireless reception unit 30 b may be the same ordifferent. The configuration of the RF unit 32 included in the wirelesstransmission unit 30 a and the configuration of the RF unit 32 includedin the wireless reception unit 30 b may be the same or different. Theconfiguration of the antenna unit 31 included in the wirelesstransmission unit 30 a and the configuration of the antenna unit 31included in the wireless reception unit 30 b may be the same ordifferent.

The higher-layer processing unit 34 provides downlink data (a transportblock) to the wireless transmission/reception unit 30 (or the wirelesstransmission unit 30 a). The higher-layer processing unit 34 performsprocessing of a medium access control (MAC) layer, a packet dataconvergence protocol layer (PDCP layer), a radio link control layer (RLClayer) and/or an RRC layer.

The medium access control layer processing unit 35 included in thehigher-layer processing unit 34 performs processing of the MAC layer.

The radio resource control layer processing unit 36 included in thehigher-layer processing unit 34 performs the process of the RRC layer.The radio resource control layer processing unit 36 manages variousconfiguration information/parameters (RRC parameters) of the terminaldevice 1. The radio resource control layer processing unit 36 configuresan RRC parameter based on the RRC message received from the terminaldevice 1.

The wireless transmission/reception unit 30 (or the wirelesstransmission unit 30 a) performs processing such as encoding andmodulation. The wireless transmission/reception unit 30 (or the wirelesstransmission unit 30 a) generates a physical signal by encoding andmodulating the downlink data. The wireless transmission/reception unit30 (or the wireless transmission unit 30 a) converts OFDM symbols in thephysical signal to a baseband signal by conversion to a time-continuoussignal. The wireless transmission/reception unit 30 (or the wirelesstransmission unit 30 a) transmits the baseband signal (or the physicalsignal) to the terminal device 1 via radio frequency. The wirelesstransmission/reception unit 30 (or the wireless transmission unit 30 a)may arrange the baseband signal (or the physical signal) on a componentcarrier and transmit the baseband signal (or the physical signal) to theterminal device 1.

The wireless transmission/reception unit 30 (or the wireless receptionunit 30 b) performs processing such as demodulation and decoding. Thewireless transmission/reception unit 30 (or the wireless reception unit30 b) separates, demodulates and decodes the received physical signal,and provides the decoded information to the higher-layer processing unit34. The wireless transmission/reception unit 30 (or the wirelessreception unit 30 b) may perform the channel access procedure prior tothe transmission of the physical signal.

The RF unit 32 demodulates the physical signal received via the antennaunit 31 into a baseband signal (down convert), and/or removes extrafrequency components. The RF unit 32 provides the processed analogsignal to the baseband unit 33.

The baseband unit 33 converts an analog signal (signals on radiofrequency) input from the RF unit 32 into a digital signal (a basebandsignal). The baseband unit 33 separates a portion which corresponds toCP (Cyclic Prefix) from the digital signal. The baseband unit 33performs Fast Fourier Transformation (FFT) on the digital signal fromwhich the CP has been removed. The baseband unit 33 provides thephysical signal in the frequency domain.

The baseband unit 33 performs Inverse Fast Fourier Transformation (IFFT)on downlink data to generate an OFDM symbol, adds a CP to the generatedOFDM symbol, generates a digital signal (baseband signal), and convertthe digital signal into an analog signal. The baseband unit 33 providesthe analog signal to the RF unit 32.

The RF unit 32 removes extra frequency components from the analog signal(signals on radio frequency) input from the baseband unit 33,up-converts the analog signal to a radio frequency, and transmits it viathe antenna unit 31. The RF unit 32 may have a function of controllingtransmission power. The RF unit 32 is also referred to as a transmissionpower control unit.

At least one or more serving cells (or one or more component carriers,one or more downlink component carriers, one or more uplink componentcarriers) may be configured for the terminal device 1.

Each of the serving cells set for the terminal device 1 may be any ofPCell (Primary cell), PSCell (Primary SCG cell), and SCell (SecondaryCell).

A PCell is a serving cell included in a MCG (Master Cell Group). A PCellis a cell (implemented cell) which performs an initial connectionestablishment procedure or a connection re-establishment procedure bythe terminal device 1.

A PSCell is a serving cell included in a SCG (Secondary Cell Group). APSCell is a serving cell in which random-access is performed by theterminal device 1 in a reconfiguration procedure with synchronization(Reconfiguration with synchronization).

A SCell may be included in either a MCG or a SCG.

The serving cell group (cell group) is a designation including at leastMCG and SCG. The serving cell group may include one or more servingcells (or one or more component carriers). One or more serving cells (orone or more component carriers) included in the serving cell group maybe operated by carrier aggregation.

One or more downlink BWPs may be configured for each serving cell (oreach downlink component carrier). One or more uplink BWPs may beconfigured for each serving cell (or each uplink component carrier).

Among the one or more downlink BWPs set for the serving cell (or thedownlink component carrier), one downlink BWP may be set as an activedownlink BWP (or one downlink BWP may be activated). Among the one ormore uplink BWPs set for the serving cell (or the uplink componentcarrier), one uplink BWP may be set as an active uplink BWP (or oneuplink BWP may be activated).

A PDSCH, a PDCCH, and a CSI-RS may be received in the active downlinkBWP. The terminal device 1 may receive the PDSCH, the PDCCH, and theCSI-RS in the active downlink BWP. A PUCCH and a PUSCH may be sent onthe active uplink BWP. The terminal device 1 may transmit the PUCCH andthe PUSCH in the active uplink BWP. The active downlink BWP and theactive uplink BWP are also referred to as active BWP.

The PDSCH, the PDCCH, and the CSI-RS may not be received in downlinkBWPs (inactive downlink BWPs) other than the active downlink BWP. Theterminal device 1 may not receive the PDSCH, the PDCCH, and the CSI-RSin the downlink BWPs which are other than the active downlink BWP. ThePUCCH and the PUSCH do not need to be transmitted in uplink BWPs(inactive uplink BWPs) other than the active uplink BWP. The terminaldevice 1 may not transmit the PUCCH and the PUSCH in the uplink BWPswhich is other than the active uplink BWP. The inactive downlink BWP andthe inactive uplink BWP are also referred to as inactive BWP.

Downlink BWP switching deactivates an active downlink BWP and activatesone of inactive downlink BWPs which are other than the active downlinkBWP. The downlink BWP switching may be controlled by a BWP fieldincluded in a downlink control information. The downlink BWP switchingmay be controlled based on higher-layer parameters.

Uplink BWP switching is used to deactivate an active uplink BWP andactivate any inactive uplink BWP which is other than the active uplinkBWP. Uplink BWP switching may be controlled by a BWP field included in adownlink control information. The uplink BWP switching may be controlledbased on higher-layer parameters.

Among the one or more downlink BWPs set for the serving cell, two ormore downlink BWPs may not be set as active downlink BWPs. For theserving cell, one downlink BWP may be active at a certain time.

Among the one or more uplink BWPs set for the serving cell, two or moreuplink BWPs may not be set as active uplink BWPs. For the serving cell,one uplink BWP may be active at a certain time.

FIG. 6 is a schematic block diagram showing a configuration example ofthe terminal device 1 according to an aspect of the present embodiment.As shown in FIG. 6 , the terminal device 1 includes at least a part orall of the wireless transmission/reception unit (physical layerprocessing unit) 10 and the higher-layer processing unit 14. Thewireless transmission/reception unit 10 includes at least a part or allof the antenna unit 11, the RF unit 12, and the baseband unit 13. Thehigher-layer processing unit 14 includes at least a part or all of themedium access control layer processing unit 15 and the radio resourcecontrol layer processing unit 16.

The wireless transmission/reception unit 10 includes at least a part ofor all of a wireless transmission unit 10 a and a wireless receptionunit 10 b. The configuration of the baseband unit 13 included in thewireless transmission unit 10 a and the configuration of the basebandunit 13 included in the wireless reception unit 10 b may be the same ordifferent. The configuration of the RF unit 12 included in the wirelesstransmission unit 10 a and the RF unit 12 included in the wirelessreception unit 10 b may be the same or different. The configuration ofthe antenna unit 11 included in the wireless transmission unit 10 a andthe configuration of the antenna unit 11 included in the wirelessreception unit 10 b may be the same or different.

The higher-layer processing unit 14 provides uplink data (a transportblock) to the wireless transmission/reception unit 10 (or the wirelesstransmission unit 10 a). The higher-layer processing unit 14 performsprocessing of a MAC layer, a packet data integration protocol layer, aradio link control layer, and/or an RRC layer.

The medium access control layer processing unit 15 included in thehigher-layer processing unit 14 performs processing of the MAC layer.

The radio resource control layer processing unit 16 included in thehigher-layer processing unit 14 performs the process of the RRC layer.The radio resource control layer processing unit 16 manages variousconfiguration information/parameters (RRC parameters) of the terminaldevice 1. The radio resource control layer processing unit 16 configuresRRC parameters based on the RRC message received from the base stationdevice 3.

The wireless transmission/reception unit 10 (or the wirelesstransmission unit 10 a) performs processing such as encoding andmodulation. The wireless transmission/reception unit 10 (or the wirelesstransmission unit 10 a) generates a physical signal by encoding andmodulating the uplink data. The wireless transmission/reception unit 10(or the wireless transmission unit 10 a) converts OFDM symbols in thephysical signal to a baseband signal by conversion to a time-continuoussignal. The wireless transmission/reception unit 10 (or the wirelesstransmission unit 10 a) transmits the baseband signal (or the physicalsignal) to the base station device 3 via radio frequency. The wirelesstransmission/reception unit 10 (or the wireless transmission unit 10 a)may arrange the baseband signal (or the physical signal) on a BWP(active uplink BWP) and transmit the baseband signal (or the physicalsignal) to the base station device 3.

The wireless transmission/reception unit 10 (or the wireless receptionunit 10 b) performs processing such as demodulation and decoding. Thewireless transmission/reception unit 10 (or the wireless reception unit10 b) may receive a physical signal in a BWP (active downlink BWP) of aserving cell. The wireless transmission/reception unit 10 (or thewireless reception unit 10 b) separates, demodulates and decodes thereceived physical signal, and provides the decoded information to thehigher-layer processing unit 14. The wireless transmission/receptionunit 10 (or the wireless reception unit 10 b) may perform the channelaccess procedure prior to the transmission of the physical signal.

The RF unit 12 demodulates the physical signal received via the antennaunit 11 into a baseband signal (down convert), and/or removes extrafrequency components. The RF unit 12 provides the processed analogsignal to the baseband unit 13.

The baseband unit 13 converts an analog signal (signals on radiofrequency) input from the RF unit 12 into a digital signal (a basebandsignal). The baseband unit 13 separates a portion which corresponds toCP from the digital signal, performs fast Fourier transformation on thedigital signal from which the CP has been removed, and provides thephysical signal in the frequency domain.

The baseband unit 13 performs inverse fast Fourier transformation onuplink data to generate an OFDM symbol, adds a CP to the generated OFDMsymbol, generates a digital signal (baseband signal), and convert thedigital signal into an analog signal. The baseband unit 13 provides theanalog signal to the RF unit 12.

The RF unit 12 removes extra frequency components from the analog signal(signals on radio frequency) input from the baseband unit 13,up-converts the analog signal to a radio frequency, and transmits it viathe antenna unit 11 The RF unit 12 may have a function of controllingtransmission power. The RF unit 12 is also referred to as a transmissionpower control unit.

Hereinafter, physical signals (signals) will be described.

Physical signal is a generic term for downlink physical channels,downlink physical signals, uplink physical channels, and uplink physicalchannels. The physical channel is a generic term for downlink physicalchannels and uplink physical channels.

An uplink physical channel may correspond to a set of resource elementsthat carry information originating from the higher-layer and/or uplinkcontrol information. The uplink physical channel may be a physicalchannel used in an uplink component carrier. The uplink physical channelmay be transmitted by the terminal device 1. The uplink physical channelmay be received by the base station device 3. In the wirelesscommunication system according to one aspect of the present embodiment,at least part or all of PUCCH (Physical Uplink Control CHannel), PUSCH(Physical Uplink Shared CHannel), and PRACH (Physical Random AccessCHannel) may be used.

A PUCCH may be used to transmit uplink control information (UCI). ThePUCCH may be sent to deliver (transmission, convey) uplink controlinformation. The uplink control information may be mapped to (orarranged in) the PUCCH. The terminal device 1 may transmit PUCCH inwhich uplink control information is arranged. The base station device 3may receive the PUCCH in which the uplink control information isarranged.

Uplink control information (uplink control information bit, uplinkcontrol information sequence, uplink control information type) includesat least part or all of channel state information (CSI), schedulingrequest (SR), and HARQ-ACK (Hybrid Automatic Repeat requestACKnowledgement).

Channel state information is conveyed by using channel state informationbits or a channel state information sequence. Scheduling request is alsoreferred to as a scheduling request bit or a scheduling requestsequence. HARQ-ACK information is also referred to as a HARQ-ACKinformation bit or a HARQ-ACK information sequence.

HARQ-ACK information may include HARQ-ACK status which corresponds to atransport block (TB: Transport block, MAC PDU: Medium Access ControlProtocol Data Unit, DL-SCH: Downlink-Shared Channel, UL-SCH:Uplink-Shared Channel, PDSCH: Physical Downlink Shared CHannel, PUSCH:Physical Uplink Shared CHannel). The HARQ-ACK status may indicate ACK(acknowledgement) or NACK (negative-acknowledgement) corresponding tothe transport block. The ACK may indicate that the transport block hasbeen successfully decoded. The NACK may indicate that the transportblock has not been successfully decoded. The HARQ-ACK information mayinclude a HARQ-ACK codebook that includes one or more HARQ-ACK status(or HARQ-ACK bits).

For example, the correspondence between the HARQ-ACK information and thetransport block may mean that the HARQ-ACK information and the PDSCHused for transmission of the transport block correspond.

HARQ-ACK status may indicate ACK or NACK which correspond to one CBG(Code Block Group) included in the transport block.

The scheduling request may at least be used to request PUSCH (or UL-SCH)resources for new transmission. The scheduling request may be used toindicate either a positive SR or a negative SR. The fact that thescheduling request indicates a positive SR is also referred to as “apositive SR is sent”. The positive SR may indicate that the PUSCH (orUL-SCH) resource for initial transmission is requested by the terminaldevice 1. A positive SR may indicate that a higher-layer is to trigger ascheduling request. The positive SR may be sent when the higher-layerinstructs to send a scheduling request. The fact that the schedulingrequest bit indicates a negative SR is also referred to as “a negativeSR is sent”. A negative SR may indicate that the PUSCH (or UL-SCH)resource for initial transmission is not requested by the terminaldevice 1. A negative SR may indicate that the higher-layer does nottrigger a scheduling request. A negative SR may be sent if thehigher-layer is not instructed to send a scheduling request.

The channel state information may include at least part or all of achannel quality indicator (CQI), a precoder matrix indicator (PMI), anda rank indicator (RI). CQI is an indicator related to channel quality(e.g., propagation quality) or physical channel quality, and PMI is anindicator related to a precoder. RI is an indicator related totransmission rank (or the number of transmission layers).

Channel state information may be provided at least based on receivingone or more physical signals (e.g., one or more CSI-RSs) used at leastfor channel measurement. The channel state information may be selectedby the terminal device 1 at least based on receiving one or morephysical signals used for channel measurement. Channel measurements mayinclude interference measurements.

A PUCCH may correspond to a PUCCH format. A PUCCH may be a set ofresource elements used to convey a PUCCH format. A PUCCH may include aPUCCH format. A PUCCH format may include UCI.

A PUSCH may be used to transmit uplink data (a transport block) and/oruplink control information. A PUSCH may be used to transmit uplink data(a transport block) corresponding to a UL-SCH and/or uplink controlinformation. A PUSCH may be used to convey uplink data (a transportblock) and/or uplink control information. A PUSCH may be used to conveyuplink data (a transport block) corresponding to a UL-SCH and/or uplinkcontrol information. Uplink data (a transport block) may be arranged ina PUSCH. Uplink data (a transport block) corresponding to UL-SCH may bearranged in a PUSCH. Uplink control information may be arranged to aPUSCH. The terminal device 1 may transmit a PUSCH in which uplink data(a transport block) and/or uplink control information is arranged. Thebase station device 3 may receive a PUSCH in which uplink data (atransport block) and/or uplink control information is arranged.

A PRACH may be used to transmit a random-access preamble. The PRACH maybe used to convey a random-access preamble. The sequence x_(u,v) (n) ofthe PRACH is defined by x_(u,v) (n)=x_(u)(mod (n+C_(v), L_(RA))). Thex_(u) may be a ZC sequence (Zadoff-Chu sequence). The x_(u) may bedefined by x_(u)=exp (−jpui (i+1)/L_(RA)). The j is an imaginary unit.The p is the circle ratio. The C_(v) corresponds to cyclic shift of thePRACH. L_(RA) corresponds to the length of the PRACH. The L_(RA) may be839 or 139 or another value. The i is an integer in the range of 0 toL_(RA)−1. The u is a sequence index for the PRACH. The terminal device 1may transmit the PRACH. The base station device 3 may receive the PRACH.

For a given PRACH opportunity, 64 random-access preambles are defined.The random-access preamble is specified (determined, given) at leastbased on the cyclic shift C_(v) of the PRACH and the sequence index ufor the PRACH.

An uplink physical signal may correspond to a set of resource elements.The uplink physical signal may not carry information generated in thehigher-layer. The uplink physical signal may be a physical signal usedin the uplink component carrier. The terminal device 1 may transmit anuplink physical signal. The base station device 3 may receive the uplinkphysical signal. In the radio communication system according to oneaspect of the present embodiment, at least a part or all of UL DMRS(UpLink Demodulation Reference Signal), SRS (Sounding Reference Signal),UL PTRS (UpLink Phase Tracking Reference Signal) may be used.

UL DMRS is a generic name of a DMRS for a PUSCH and a DMRS for a PUCCH.

A set of antenna ports of a DMRS for a PUSCH (a DMRS associated with aPUSCH, a DMRS included in a PUSCH, a DMRS which corresponds to a PUSCH)may be given based on a set of antenna ports for the PUSCH. That is, theset of DMRS antenna ports for the PUSCH may be the same as the set ofantenna ports for the PUSCH.

Transmission of a PUSCH and transmission of a DMRS for the PUSCH may beindicated (or scheduled) by one DCI format. The PUSCH and the DMRS forthe PUSCH may be collectively referred to as a PUSCH. Transmission ofthe PUSCH may be transmission of the PUSCH and the DMRS for the PUSCH.

A PUSCH may be estimated from a DMRS for the PUSCH. That is, propagationpath of the PUSCH may be estimated from the DMRS for the PUSCH.

A set of antenna ports of a DMRS for a PUCCH (a DMRS associated with aPUCCH, a DMRS included in a PUCCH, a DMRS which corresponds to a PUCCH)may be identical to a set of antenna ports for the PUCCH.

Transmission of a PUCCH and transmission of a DMRS for the PUCCH may beindicated (or triggered) by one DCI format. The arrangement of the PUCCHin resource elements (resource element mapping) and/or the arrangementof the DMRS in resource elements for the PUCCH may be provided at leastby one PUCCH format. The PUCCH and the DMRS for the PUCCH may becollectively referred to as PUCCH. Transmission of the PUCCH may betransmission of the PUCCH and the DMRS for the PUCCH.

A PUCCH may be estimated from a DMRS for the PUCCH. That is, propagationpath of the PUCCH may be estimated from the DMRS for the PUCCH.

A downlink physical channel may correspond to a set of resource elementsthat carry information originating from the higher-layer and/or downlinkcontrol information. The downlink physical channel may be a physicalchannel used in the downlink component carrier. The base station device3 may transmit the downlink physical channel. The terminal device 1 mayreceive the downlink physical channel. In the wireless communicationsystem according to one aspect of the present embodiment, at least apart or all of PBCH (Physical Broadcast Channel), PDCCH (PhysicalDownlink Control Channel), and PDSCH (Physical Downlink Shared Channel)may be used.

The PBCH may be used to transmit a MIB (Master Information Block) and/orphysical layer control information. The physical layer controlinformation is a kind of downlink control information. The PBCH may besent to deliver the MIB and/or the physical layer control information. ABCH may be mapped (or corresponding) to the PBCH. The terminal device 1may receive the PBCH. The base station device 3 may transmit the PBCH.The physical layer control information is also referred to as a PBCHpayload and a PBCH payload related to timing. The MIB may include one ormore higher-layer parameters.

Physical layer control information includes 8 bits. The physical layercontrol information may include at least part or all of 0A to 0D. The 0Ais radio frame information. The 0B is half radio frame information (halfsystem frame information). The 0C is SS/PBCH block index information.The 0D is subcarrier offset information.

The radio frame information is used to indicate a radio frame in whichthe PBCH is transmitted (a radio frame including a slot in which thePBCH is transmitted). The radio frame information is represented by 4bits. The radio frame information may be represented by 4 bits of aradio frame indicator. The radio frame indicator may include 10 bits.For example, the radio frame indicator may at least be used to identifya radio frame from index 0 to index 1023.

The half radio frame information is used to indicate whether the PBCH istransmitted in first five subframes or in second five subframes amongradio frames in which the PBCH is transmitted. Here, the half radioframe may be configured to include five subframes. The half radio framemay be configured by five subframes of the first half of ten subframesincluded in the radio frame. The half radio frame may be configured byfive subframes in the second half of ten subframes included in the radioframe.

The SS/PBCH block index information is used to indicate an SS/PBCH blockindex. The SS/PBCH block index information may be represented by 3 bits.The SS/PBCH block index information may consist of 3 bits of an SS/PBCHblock index indicator. The SS/PBCH block index indicator may include 6bits. The SS/PBCH block index indicator may at least be used to identifyan SS/PBCH block from index 0 to index 63 (or from index 0 to index 3,from index 0 to index 7, from index 0 to index 9, from index 0 to index19, etc.).

The subcarrier offset information is used to indicate subcarrier offset.The subcarrier offset information may be used to indicate the differencebetween the first subcarrier in which the PBCH is arranged and the firstsubcarrier in which the control resource set with index 0 is arranged.

A PDCCH may be used to transmit downlink control information (DCI). APDCCH may be transmitted to deliver downlink control information.Downlink control information may be mapped to a PDCCH. The terminaldevice 1 may receive a PDCCH in which downlink control information isarranged. The base station device 3 may transmit the PDCCH in which thedownlink control information is arranged.

Downlink control information may correspond to a DCI format. Downlinkcontrol information may be included in a DCI format. Downlink controlinformation may be arranged in each field of a DCI format.

DCI format is a generic name for DCI format 0_0, DCI format 0_1, DCIformat 1_0, and DCI format 1_1. Uplink DCI format is a generic name ofthe DCI format 0_0 and the DCI format 0_1. Downlink DCI format is ageneric name of the DCI format 1_0 and the DCI format 1_1.

The DCI format 0_0 is at least used for scheduling a PUSCH for a cell(or a PUSCH arranged on a cell). The DCI format 0_0 includes at least apart or all of fields 1A to 1E. The 1A is a DCI format identificationfield (Identifier field for DCI formats). The 1B is a frequency domainresource assignment field (FDRA field, FDRA information field). The 1Cis a time domain resource assignment field (TDRA field, TDRA informationfield). The 1D is a frequency-hopping flag field. The 1E is an MCS field(Modulation-and-Coding-Scheme field).

Frequency domain resource assignment field may be referred to as FDRAfield or FDRA information field.

Time domain resource assignment field may be referred to as TDRA fieldor TDRA information field.

The DCI format identification field may indicate whether the DCI formatincluding the DCI format identification field is an uplink DCI format ora downlink DCI format. The DCI format identification field included inthe DCI format 0_0 may indicate 0 (or may indicate that the DCI format0_0 is an uplink DCI format).

The frequency domain resource assignment field included in the DCIformat 0_0 may be at least used to indicate the assignment (allocation)of frequency resources for a PUSCH. The frequency domain resourceassignment field included in the DCI format 0_0 may be at least used toindicate the assignment (allocation) of frequency resources for a PUSCHscheduled by the DCI format 0_0.

The time domain resource assignment field included in the DCI format 0_0may be at least used to indicate the assignment of time resources for aPUSCH. The time domain resource assignment field included in the DCIformat 0_0 may be at least used to indicate the assignment of timeresources for a PUSCH scheduled by the DCI format 0_0.

The frequency-hopping flag field may be at least used to indicatewhether frequency-hopping is applied to a PUSCH. The frequency-hoppingflag field may be at least used to indicate whether frequency-hopping isapplied to a PUSCH scheduled by the DCI format 0_0.

The MCS field included in the DCI format 0_0 may be at least used toindicate a modulation scheme for a PUSCH and/or a part or all of atarget coding rate for the PUSCH. The MCS field included in the DCIformat 0_0 may be at least used to indicate a modulation scheme for aPUSCH scheduled by the DCI format 0_0 and/or a part or all of a targetcoding rate for the PUSCH. A size of a transport block (TBS: TransportBlock Size) of a PUSCH may be given based at least on a target codingrate and a part or all of a modulation scheme for the PUSCH.

The DCI format 0_0 may not include fields used for a CSI request. Thatis, CSI may not be requested by the DCI format 0_0.

The DCI format 0_0 may not include a carrier indicator field. An uplinkcomponent carrier on which a PUSCH scheduled by the DCI format 0_0 isarranged may be the same as an uplink component carrier on which a PDCCHincluding the DCI format 0_0 is arranged.

The DCI format 0_0 may not include a BWP field. An uplink BWP on which aPUSCH scheduled by the DCI format 0_0 is arranged may be the same as anuplink BWP on which a PDCCH including the DCI format 0_0 is arranged.

The DCI format 0_1 is at least used for scheduling of a PUSCH for a cell(or arranged on a cell). The DCI format 0_1 includes at least a part orall of fields 2A to 2H. The 2A is a DCI format identification field. The2B is a frequency domain resource assignment field. The 2C is a timedomain resource assignment field. The 2D is a frequency-hopping flagfield. The 2E is an MCS field. The 2F is a CSI request field. The 2G isa BWP field. The 2H is a carrier indicator field.

The DCI format identification field included in the DCI format 0_1 mayindicate 0 (or may indicate that the DCI format 0_1 is an uplink DCIformat).

The frequency domain resource assignment field included in the DCIformat 0_1 may be at least used to indicate the assignment of frequencyresources for a PUSCH. The frequency domain resource assignment fieldincluded in the DCI format 0_1 may be at least used to indicate theassignment of frequency resources for a PUSCH scheduled by the DCIformat.

The time domain resource assignment field included in the DCI format 0_1may be at least used to indicate the assignment of time resources for aPUSCH. The time domain resource assignment field included in DCI format0_1 may be at least used to indicate the assignment of time resourcesfor a PUSCH scheduled by the DCI format 0_1.

The frequency-hopping flag field may be at least used to indicatewhether frequency-hopping is applied to a PUSCH scheduled by the DCIformat 0_1.

The MCS field included in the DCI format 0_1 may be at least used toindicate a modulation scheme for a PUSCH and/or a part or all of atarget coding rate for the PUSCH. The MCS field included in the DCIformat 0_1 may be at least used to indicate a modulation scheme for aPUSCH scheduled by the DCI format and/or part or all of a target codingrate for the PUSCH.

When the DCI format 0_1 includes the BWP field, the BWP field may beused to indicate an uplink BWP on which a PUSCH scheduled by the DCIformat 0_1 is arranged. When the DCI format 0_1 does not include the BWPfield, an uplink BWP on which a PUSCH is arranged may be the activeuplink BWP. When the number of uplink BWPs configured in the terminaldevice 1 in a uplink component carrier is two or more, the number ofbits for the BWP field included in the DCI format 0_1 used forscheduling a PUSCH arranged on the uplink component carrier may be oneor more. When the number of uplink BWPs configured in the terminaldevice 1 in a uplink component carrier is one, the number of bits forthe BWP field included in the DCI format 0_1 used for scheduling a PUSCHarranged on the uplink component carrier may be zero.

The CSI request field is at least used to indicate CSI reporting.

If the DCI format 0_1 includes the carrier indicator field, the carrierindicator field may be used to indicate an uplink component carrier (ora serving cell) on which a PUSCH is arranged. When the DCI format 0_1does not include the carrier indicator field, a serving cell on which aPUSCH is arranged may be the same as the serving cell on which a PDCCHincluding the DCI format 0_1 used for scheduling of the PUSCH isarranged. When the number of uplink component carriers (or the number ofserving cells) configured in the terminal device 1 in a serving cellgroup is two or more (when uplink carrier aggregation is operated in aserving cell group), or when cross-carrier scheduling is configured forthe serving cell group, the number of bits for the carrier indicatorfield included in the DCI format 0_1 used for scheduling a PUSCHarranged on the serving cell group may be one or more (e.g., 3). Whenthe number of uplink component carriers (or the number of serving cells)configured in the terminal device 1 in a serving cell group is one (orwhen uplink carrier aggregation is not operated in a serving cellgroup), or when the cross-carrier scheduling is not configured for theserving cell group, the number of bits for the carrier indicator fieldincluded in the DCI format 0_1 used for scheduling of a PUSCH arrangedon the serving cell group may be zero.

The DCI format 1_0 is at least used for scheduling of a PDSCH for a cell(arranged on a cell). The DCI format 1_0 includes at least a part or allof fields 3A to 3F. The 3A is a DCI format identification field. The 3Bis a frequency domain resource assignment field. The 3C is a time domainresource assignment field. The 3D is an MCS field. The 3E is aPDSCH-to-HARQ-feedback indicator field. The 3F is a PUCCH resourceindicator field.

The DCI format identification field included in the DCI format 1_0 mayindicate 1 (or may indicate that the DCI format 1_0 is a downlink DCIformat).

The frequency domain resource assignment field included in the DCIformat 1_0 may be at least used to indicate the assignment of frequencyresources for a PDSCH. The frequency domain resource assignment fieldincluded in the DCI format 1_0 may be at least used to indicate theassignment of frequency resources for a PDSCH scheduled by the DCIformat 1_0.

The time domain resource assignment field included in the DCI format 1_0may be at least used to indicate the assignment of time resources for aPDSCH. The time domain resource assignment field included in the DCIformat 1_0 may be at least used to indicate the assignment of timeresources for a PDSCH scheduled by the DCI format 1_0.

The MCS field included in the DCI format 1_0 may be at least used toindicate a modulation scheme for a PDSCH and/or a part or all of atarget coding rate for the PDSCH. The MCS field included in the DCIformat 1_0 may be at least used to indicate a modulation scheme for aPDSCH scheduled by the DCI format 1_0 and/or a part or all of a targetcoding rate for the PDSCH. A size of a transport block (TBS: TransportBlock Size) of a PDSCH may be given based at least on a target codingrate and a part or all of a modulation scheme for the PDSCH.

The PDSCH-to-HARQ-feedback timing indicator field may be at least usedto indicate the offset (K1) from a slot in which the last OFDM symbol ofa PDSCH scheduled by the DCI format 1_0 is included to another slot inwhich the first OFDM symbol of a PUCCH triggered by the DCI format 1_0is included.

The PUCCH resource indicator field may be a field indicating an index ofany one or more PUCCH resources included in the PUCCH resource set for aPUCCH transmission. The PUCCH resource set may include one or more PUCCHresources. The PUCCH resource indicator field may trigger PUCCHtransmission with a PUCCH resource indicated at least based on the PUCCHresource indicator field.

The DCI format 1_0 may not include the carrier indicator field. Adownlink component carrier on which a PDSCH scheduled by the DCI format1_0 is arranged may be the same as a downlink component carrier on whicha PDCCH including the DCI format 1_0 is arranged.

The DCI format 1_0 may not include the BWP field. A downlink BWP onwhich a PDSCH scheduled by a DCI format 1_0 is arranged may be the sameas a downlink BWP on which a PDCCH including the DCI format 1_0 isarranged.

The DCI format 1_1 is at least used for scheduling of a PDSCH for a cell(or arranged on a cell). The DCI format 1_1 includes at least a part orall of fields 4A to 4H. The 4A is a DCI format identification field. The4B is a frequency domain resource assignment field. The 4C is a timedomain resource assignment field. The 4D is an MCS field. The 4E is aPDSCH-to-HARQ-feedback indicator field. The 4F is a PUCCH resourceindicator field. The 4G is a BWP field. The 4H is a carrier indicatorfield.

The DCI format identification field included in the DCI format 1_1 mayindicate 1 (or may indicate that the DCI format 1_1 is a downlink DCIformat).

The frequency domain resource assignment field included in the DCIformat 1_1 may be at least used to indicate the assignment of frequencyresources for a PDSCH. The frequency domain resource assignment fieldincluded in the DCI format 1_0 may be at least used to indicate theassignment of frequency resources for a PDSCH scheduled by the DCIformat 1_1.

The time domain resource assignment field included in the DCI format 1_1may be at least used to indicate the assignment of time resources for aPDSCH. The time domain resource assignment field included in the DCIformat 1_1 may be at least used to indicate the assignment of timeresources for a PDSCH scheduled by the DCI format 1_1.

The MCS field included in the DCI format 1_1 may be at least used toindicate a modulation scheme for a PDSCH and/or a part or all of atarget coding rate for the PDSCH. The MCS field included in the DCIformat 1_1 may be at least used to indicate a modulation scheme for aPDSCH scheduled by the DCI format 1_1 and/or a part or all of a targetcoding rate for the PDSCH.

When the DCI format 1_1 includes a PDSCH-to-HARQ-feedback timingindicator field, the PDSCH-to-HARQ-feedback timing indicator fieldindicates an offset (K1) from a slot including the last OFDM symbol of aPDSCH scheduled by the DCI format 1_1 to another slot including thefirst OFDM symbol of a PUCCH triggered by the DCI format 1_1. When theDCI format 1_1 does not include the PDSCH-to-HARQ-feedback timingindicator field, an offset from a slot in which the last OFDM symbol ofa PDSCH scheduled by the DCI format 1_1 is included to another slot inwhich the first OFDM symbol of a PUCCH triggered by the DCI format 1_1is identified by a higher-layer parameter.

When the DCI format 1_1 includes the BWP field, the BWP field may beused to indicate a downlink BWP on which a PDSCH scheduled by the DCIformat 1_1 is arranged. When the DCI format 1_1 does not include the BWPfield, a downlink BWP on which a PDSCH is arranged may be the activedownlink BWP. When the number of downlink BWPs configured in theterminal device 1 in a downlink component carrier is two or more, thenumber of bits for the BWP field included in the DCI format 1_1 used forscheduling a PDSCH arranged on the downlink component carrier may be oneor more. When the number of downlink BWPs configured in the terminaldevice 1 in a downlink component carrier is one, the number of bits forthe BWP field included in the DCI format 1_1 used for scheduling a PDSCHarranged on the downlink component carrier may be zero.

If the DCI format 1_1 includes the carrier indicator field, the carrierindicator field may be used to indicate a downlink component carrier (ora serving cell) on which a PDSCH is arranged. When the DCI format 1_1does not include the carrier indicator field, a downlink componentcarrier (or a serving cell) on which a PDSCH is arranged may be the sameas a downlink component carrier (or a serving cell) on which a PDCCHincluding the DCI format 1_1 used for scheduling of the PDSCH isarranged. When the number of downlink component carriers (or the numberof serving cells) configured in the terminal device 1 in a serving cellgroup is two or more (when downlink carrier aggregation is operated in aserving cell group), or when cross-carrier scheduling is configured forthe serving cell group, the number of bits for the carrier indicatorfield included in the DCI format 1_1 used for scheduling a PDSCHarranged on the serving cell group may be one or more (e.g., 3). Whenthe number of downlink component carriers (or the number of servingcells) configured in the terminal device 1 in a serving cell group isone (or when downlink carrier aggregation is not operated in a servingcell group), or when the cross-carrier scheduling is not configured forthe serving cell group, the number of bits for the carrier indicatorfield included in the DCI format 1_1 used for scheduling of a PDSCHarranged on the serving cell group may be zero.

A PDSCH may be used to transmit one or more transport blocks. A PDSCHmay be used to transmit one or more transport blocks which correspondsto a DL-SCH. A PDSCH may be used to convey one or more transport blocks.A PDSCH may be used to convey one or more transport blocks whichcorresponds to a DL-SCH. One or more transport blocks may be arranged ina PDSCH. One or more transport blocks which corresponds to a DL-SCH maybe arranged in a PDSCH. The base station device 3 may transmit a PDSCH.The terminal device 1 may receive the PDSCH.

Downlink physical signals may correspond to a set of resource elements.The downlink physical signals may not carry the information generated inthe higher-layer. The downlink physical signals may be physical signalsused in the downlink component carrier. A downlink physical signal maybe transmitted by the base station device 3. The downlink physicalsignal may be transmitted by the terminal device 1. In the wirelesscommunication system according to one aspect of the present embodiment,at least a part or all of an SS (Synchronization signal), DL DMRS(DownLink DeModulation Reference Signal), CSI-RS (Channel StateInformation-Reference Signal), and DL PTRS (DownLink Phase TrackingReference Signal) may be used.

The synchronization signal may be used at least for the terminal device1 to synchronize in the frequency domain and/or time domain fordownlink. The synchronization signal is a generic name of PSS (PrimarySynchronization Signal) and SSS (Secondary Synchronization Signal).

FIG. 7 is a diagram showing a configuration example of an SS/PBCH blockaccording to an aspect of the present embodiment. In FIG. 7 , thehorizontal axis indicates time domain (OFDM symbol index l_(sym)), andthe vertical axis indicates frequency domain. The shaded blocks indicatea set of resource elements for a PSS. The blocks of grid lines indicatea set of resource elements for an SSS. Also, the blocks in thehorizontal line indicate a set of resource elements for a PBCH and a setof resource elements for a DMRS for the PBCH (DMRS related to the PBCH,DMRS included in the PBCH, DMRS which corresponds to the PBCH).

As shown in FIG. 7 , the SS/PBCH block includes a PSS, an SSS, and aPBCH. The SS/PBCH block includes 4 consecutive OFDM symbols. The SS/PBCHblock includes 240 subcarriers. The PSS is allocated to the 57th to183rd subcarriers in the first OFDM symbol. The SSS is allocated to the57th to 183rd subcarriers in the third OFDM symbol. The first to 56thsubcarriers of the first OFDM symbol may be set to zero. The 184th to240th subcarriers of the first OFDM symbol may be set to zero. The 49thto 56th subcarriers of the third OFDM symbol may be set to zero. The184th to 192nd subcarriers of the third OFDM symbol may be set to zero.In the first to 240th subcarriers of the second OFDM symbol, the PBCH isallocated to subcarriers in which the DMRS for the PBCH is notallocated. In the first to 48th subcarriers of the third OFDM symbol,the PBCH is allocated to subcarriers in which the DMRS for the PBCH isnot allocated. In the 193rd to 240th subcarriers of the third OFDMsymbol, the PBCH is allocated to subcarriers in which the DMRS for thePBCH is not allocated. In the first to 240th subcarriers of the 4th OFDMsymbol, the PBCH is allocated to subcarriers in which the DMRS for thePBCH is not allocated.

The antenna ports of a PSS, an SSS, a PBCH, and a DMRS for the PBCH inan SS/PBCH block may be identical.

A PBCH may be estimated from a DMRS for the PBCH. For the DM-RS for thePBCH, the channel over which a symbol for the PBCH on an antenna port isconveyed can be inferred from the channel over which another symbol forthe DM-RS on the antenna port is conveyed only if the two symbols arewithin a SS/PBCH block transmitted within the same slot, and with thesame SS/PBCH block index.

DL DMRS is a generic name of DMRS for a PBCH, DMRS for a PDSCH, and DMRSfor a PDCCH.

A set of antenna ports for a DMRS for a PDSCH (a DMRS associated with aPDSCH, a DMRS included in a PDSCH, a DMRS which corresponds to a PDSCH)may be given based on the set of antenna ports for the PDSCH. The set ofantenna ports for the DMRS for the PDSCH may be the same as the set ofantenna ports for the PDSCH.

Transmission of a PDSCH and transmission of a DMRS for the PDSCH may beindicated (or scheduled) by one DCI format. The PDSCH and the DMRS forthe PDSCH may be collectively referred to as PDSCH. Transmitting a PDSCHmay be transmitting a PDSCH and a DMRS for the PDSCH.

A PDSCH may be estimated from a DMRS for the PDSCH. For a DM-RSassociated with a PDSCH, the channel over which a symbol for the PDSCHon one antenna port is conveyed can be inferred from the channel overwhich another symbol for the DM-RS on the antenna port is conveyed onlyif the two symbols are within the same resource as the scheduled PDSCH,in the same slot, and in the same PRG (Precoding Resource Group).

Antenna ports for a DMRS for a PDCCH (a DMRS associated with a PDCCH, aDMRS included in a PDCCH, a DMRS which corresponds to a PDCCH) may bethe same as an antenna port for the PDCCH.

A PDCCH may be estimated from a DMRS for the PDCCH. For a DM-RSassociated with a PDCCH, the channel over which a symbol for the PDCCHon one antenna port is conveyed can be inferred from the channel overwhich another symbol for the DM-RS on the same antenna port is conveyedonly if the two symbols are within resources for which the UE may assumethe same precoding being used (i.e. within resources in a REG bundle).

A BCH (Broadcast CHannel), a UL-SCH (Uplink-Shared CHannel) and a DL-SCH(Downlink-Shared CHannel) are transport channels. A channel used in theMAC layer is called a transport channel. A unit of transport channelused in the MAC layer is also called transport block (TB) or MAC PDU(Protocol Data Unit). In the MAC layer, control of HARQ (HybridAutomatic Repeat request) is performed for each transport block. Thetransport block is a unit of data delivered by the MAC layer to thephysical layer. In the physical layer, transport blocks are mapped tocodewords and modulation processing is performed for each codeword.

One UL-SCH and one DL-SCH may be provided for each serving cell. BCH maybe given to PCell. BCH may not be given to PSCell and SCell.

A BCCH (Broadcast Control CHannel), a CCCH (Common Control CHannel), anda DCCH (Dedicated Control CHannel) are logical channels. The BCCH is achannel of the RRC layer used to deliver MIB or system information. TheCCCH may be used to transmit a common RRC message in a plurality ofterminal devices 1. The CCCH may be used for the terminal device 1 whichis not connected by RRC. The DCCH may be used at least to transmit adedicated RRC message to the terminal device 1. The DCCH may be used forthe terminal device 1 that is in RRC-connected mode.

The RRC message includes one or more RRC parameters (informationelements, higher layer parameters). For example, the RRC message mayinclude a MIB. For example, the RRC message may include systeminformation (SIB: System Information Block, MIB). SIB is a generic namefor various type of SIBs (e.g., SIB1, SIB2). For example, the RRCmessage may include a message which corresponds to a CCCH. For example,the RRC message may include a message which corresponds to a DCCH. RRCmessage is a general term for common RRC message and dedicated RRCmessage.

The BCCH in the logical channel may be mapped to the BCH or the DL-SCHin the transport channel. The CCCH in the logical channel may be mappedto the DL-SCH or the UL-SCH in the transport channel. The DCCH in thelogical channel may be mapped to the DL-SCH or the UL-SCH in thetransport channel.

The UL-SCH in the transport channel may be mapped to a PUSCH in thephysical channel. The DL-SCH in the transport channel may be mapped to aPDSCH in the physical channel. The BCH in the transport channel may bemapped to a PBCH in the physical channel.

A higher-layer parameter is a parameter included in an RRC message or aMAC CE (Medium Access Control Control Element). The higher-layerparameter is a generic name of information included in a MIB, systeminformation, a message which corresponds to CCCH, a message whichcorresponds to DCCH, and a MAC CE. A higher-layer parameter may bereferred to as an RRC parameter or an RRC configuration if thehigher-layer parameter is the parameter included in the RRC message.

A higher-layer parameter may be a cell-specific parameter or aUE-specific parameter. A cell-specific parameter is a parameterincluding a common configuration in a cell. A UE-specific parameter is aparameter including a configuration that may be configured differentlyfor each UE.

The base station device may indicate change of cell-specific parametersby reconfiguration with random-access. The UE may change cell-specificparameters before triggering random-access. The base station device mayindicate change of UE-specific parameters by reconfiguration with orwithout random-access. The UE may change UE-specific parameters beforeor after random-access.

The procedure performed by the terminal device 1 includes at least apart or all of the following 5A to 5C. The 5A is cell search. The 5B israndom-access. The 5C is data communication.

The cell search is a procedure used by the terminal device 1 tosynchronize with a cell in the time domain and/or the frequency domainand to detect a physical cell identity (ID). The terminal device 1 maydetect the physical cell ID by performing synchronization of time domainand/or frequency domain with a cell by the cell search using the cell'sPSS and SSS. The detected physical cell ID is the physical cell ID ofthe cell. When the cell is a serving cell, the detected physical cell IDis the serving cell's physical cell ID.

A sequence of a PSS is given based at least on a physical cell ID. Asequence of an SSS is given based at least on the physical cell ID.

An SS/PBCH block candidate indicates a resource for which transmissionof the SS/PBCH block may exist. An SS/PBCH block may be transmitted at aresource indicated as the SS/PBCH block candidate. The base stationdevice 3 may transmit an SS/PBCH block at an SS/PBCH block candidate.The terminal device 1 may receive (detect) the SS/PBCH block at theSS/PBCH block candidate.

A set of SS/PBCH block candidates in a half radio frame is also referredto as an SS-burst-set. The SS-burst-set is also referred to as atransmission window, a SS transmission window, or a DRS transmissionwindow (Discovery Reference Signal transmission window). TheSS-burst-set is a generic name that includes at least a firstSS-burst-set and a second SS-burst-set.

The base station device 3 transmits SS/PBCH blocks of one or moreindexes at a predetermined cycle. The terminal device 1 may detect anSS/PBCH block of at least one of the SS/PBCH blocks of the one or moreindexes. The terminal device 1 may attempt to decode the PBCH includedin the SS/PBCH block.

The random-access is a procedure including at least a part or all ofmessage 1, message 2, message 3, and message 4.

The message 1 is a procedure in which the terminal device 1 transmits aPRACH. The terminal device 1 transmits the PRACH in one PRACH occasionselected from among one or more PRACH occasions based on at least theindex of the SS/PBCH block candidate detected based on the cell search.

The message 2 is a procedure in which the terminal device 1 attempts todetect a DCI format 1_0 with CRC (Cyclic Redundancy Check) scrambled byan RA-RNTI (Random Access-Radio Network Temporary Identifier). Theterminal device 1 may attempt to detect the DCI format 1_0 in asearch-space-set.

The message 3 (Msg 3) is a procedure for transmitting a PUSCH scheduledby a random-access response grant included in the DCI format 1_0detected in the message 2 procedure. The random-access response grant isindicated by the MAC CE included in the PDSCH scheduled by the DCIformat 1_0.

The PUSCH scheduled based on the random-access response grant is eithera message 3 PUSCH or a PUSCH. The message 3 PUSCH contains a contentionresolution identifier MAC CE. The contention resolution ID MAC CEincludes a contention resolution ID.

Retransmission of the message 3 PUSCH is scheduled by DCI format 0_0with CRC scrambled by a TC-RNTI (Temporary Cell-Radio Network TemporaryIdentifier).

The message 4 is a procedure that attempts to detect a DCI format 1_0with CRC scrambled by either a C-RNTI (Cell-Radio Network TemporaryIdentifier) or a TC-RNTI. The terminal device 1 receives a PDSCHscheduled based on the DCI format 1_0. The PDSCH may include a collisionresolution ID.

Data communication is a generic term for downlink communication anduplink communication.

In data communication, the terminal device 1 attempts to detect a PDCCH(attempts to monitor a PDCCH, monitors a PDCCH). in a resourceidentified at least based on one or all of a control resource set and asearch-space-set. It's also called as “the terminal device 1 attempts todetect a PDCCH in a control resource set”, “the terminal device 1attempts to detect a PDCCH in a search-space-set”, “the terminal device1 attempts to detect a PDCCH candidate in a control resource set”, “theterminal device 1 attempts to detect a PDCCH candidate in asearch-space-set”, “the terminal device 1 attempts to detect a DCIformat in a control resource set”, or “the terminal device 1 attempts todetect a DCI format in a search-space-set”. Monitoring a PDCCH may beequivalent as monitoring a DCI format in the PDCCH.

The control resource set is a set of resources configured by the numberof resource blocks and a predetermined number of OFDM symbols in a slot.

The set of resources for the control resource set may be indicated byhigher-layer parameters. The number of OFDM symbols included in thecontrol resource set may be indicated by higher-layer parameters.

A PDCCH may be also called as a PDCCH candidate.

A search-space-set is defined as a set of PDCCH candidates. Asearch-space-set may be a Common Search Space (CSS) set or a UE-specificSearch Space (USS) set.

The CSS set is a generic name of a type-0 PDCCH common search-space-set,a type-0a PDCCH common search-space-set, a type-1 PDCCH commonsearch-space-set, a type-2 PDCCH common search-space-set, and a type-3PDCCH common search-space-set. The USS set may be also called asUE-specific PDCCH search-space-set.

The type-0 PDCCH common search-space-set may be used as a commonsearch-space-set with index 0. The type-0 PDCCH common search-space-setmay be an common search-space-set with index 0.

A search-space-set is associated with (included in, corresponding to) acontrol resource set. The index of the control resource set associatedwith the search-space-set may be indicated by higher-layer parameters.

For a search-space-set, a part or all of 6A to 6C may be indicated atleast by higher-layer parameters. The 6A is PDCCH monitoring period. The6B is PDCCH monitoring pattern within a slot. The 6C is PDCCH monitoringoffset.

A monitoring occasion of a search-space-set may correspond to one ormore OFDM symbols in which the first OFDM symbol of the control resourceset associated with the search-space-set is allocated. A monitoringoccasion of a search-space-set may correspond to resources identified bythe first OFDM symbol of the control resource set associated with thesearch-space-set. A monitoring occasion of a search-space-set is givenbased at least on a part or all of PDCCH monitoring periodicity, PDCCHmonitoring pattern within a slot, and PDCCH monitoring offset.

FIG. 8 is a diagram showing an example of the monitoring occasion of thesearch-space-set according to an aspect of the present embodiment. InFIG. 8 , the search-space-set 91 and the search-space-set 92 are sets inthe primary cell 301, the search-space-set 93 is a set in the secondarycell 302, and the search-space-set 94 is a set in the secondary cell303.

In FIG. 8 , the block indicated by the grid line indicates thesearch-space-set 91, the block indicated by the upper right diagonalline indicates the search-space-set 92, the block indicated by the upperleft diagonal line indicates the search-space-set 93, and the blockindicated by the horizontal line indicates the search-space-set 94.

In FIG. 8 , the PDCCH monitoring periodicity for the search-space-set 91is set to 1 slot, the PDCCH monitoring offset for the search-space-set91 is set to 0 slot, and the PDCCH monitoring pattern for thesearch-space-set 91 is [1, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0]. Thatis, the monitoring occasion of the search-space-set 91 corresponds tothe first OFDM symbol (OFDM symbol #0) and the eighth OFDM symbol (OFDMsymbol #7) in each of the slots.

In FIG. 8 , the PDCCH monitoring periodicity for the search-space-set 92is set to 2 slots, the PDCCH monitoring offset for the search-space-set92 is set to 0 slots, and the PDCCH monitoring pattern for thesearch-space-set 92 is [1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]. Thatis, the monitoring occasion of the search-space-set 92 corresponds tothe leading OFDM symbol (OFDM symbol #0) in each of the even slots.

In FIG. 8 , the PDCCH monitoring periodicity for the search-space-set 93is set to 2 slots, the PDCCH monitoring offset for the search-space-set93 is set to 0 slots, and the PDCCH monitoring pattern for thesearch-space-set 93 is [0, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0]. Thatis, the monitoring occasion of the search-space-set 93 corresponds tothe eighth OFDM symbol (OFDM symbol #8) in each of the even slots.

In FIG. 8 , the PDCCH monitoring periodicity for the search-space-set 94is set to 2 slots, the PDCCH monitoring offset for the search-space-set94 is set to 1 slot, and the PDCCH monitoring pattern for thesearch-space-set 94 is [1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]. Thatis, the monitoring occasion of the search-space-set 94 corresponds tothe leading OFDM symbol (OFDM symbol #0) in each of the odd slots.

The type-0 PDCCH common search-space-set may be at least used for a DCIformat with a cyclic redundancy check (CRC) sequence scrambled by anSI-RNTI (System Information-Radio Network Temporary Identifier).

The type-0a PDCCH common search-space-set may be used at least for a DCIformat with a cyclic redundancy check sequence scrambled by an SI-RNTI.

The type-1 PDCCH common search-space-set may be used at least for a DCIformat with a CRC sequence scrambled by an RA-RNTI (Random Access-RadioNetwork Temporary Identifier) or a CRC sequence scrambled by a TC-RNTI(Temporary Cell-Radio Network Temporary Identifier).

The type-2 PDCCH common search-space-set may be used for a DCI formatwith a CRC sequence scrambled by P-RNTI (Paging-Radio Network TemporaryIdentifier).

The type-3 PDCCH common search-space-set may be used for a DCI formatwith a CRC sequence scrambled by a C-RNTI (Cell-Radio Network TemporaryIdentifier).

The UE-specific search-space-set may be used at least for a DCI formatwith a CRC sequence scrambled by a C-RNTI.

In downlink communication, the terminal device 1 may detect a downlinkDCI format. The detected downlink DCI format is at least used forresource assignment for a PDSCH. The detected downlink DCI format isalso referred to as downlink assignment. The terminal device 1 attemptsto receive the PDSCH. Based on a PUCCH resource indicated based on thedetected downlink DCI format, an HARQ-ACK corresponding to the PDSCH(HARQ-ACK corresponding to a transport block included in the PDSCH) maybe reported to the base station device 3.

In uplink communication, the terminal device 1 may detect an uplink DCIformat. The detected uplink DCI format is at least used for resourceassignment for a PUSCH. The detected uplink DCI format is also referredto as uplink grant. The terminal device 1 transmits the PUSCH.

PUSCH transmission(s) can be dynamically scheduled by an UL grant in aDCI, or the transmission can correspond to a configured grant Type 1 orType 2. The configured grant Type 1 PUSCH transmission issemi-statically configured to operate upon the reception of higher layerparameter of configuredGrantConfig including rrc-ConfiguredUplinkGrantwithout the detection of an UL grant in a DCI. The configured grant Type2 PUSCH transmission is semi-persistently scheduled by an UL grant in avalid activation DCI according to those procedure(s) after the receptionof higher layer parameter configuredGrantConfig not includingrrc-ConfiguredUplinkGrant. If configuredGrantConfigToAddModList isconfigured, more than one configured grant configuration of configuredgrant Type 1 and/or configured grant Type 2 may be active at the sametime on an active BWP of a serving cell.

More details of resource allocation in time domain for PUSCH scheduledby a DCI format is described. When the UE (terminal device 1) isscheduled to transmit a transport block and no CSI report, or the UE isscheduled to transmit a transport block and a CSI report(s) on PUSCH bya DCI, the ‘Time domain resource assignment’ field value m of the DCImay provide a row index m+1 to an allocated table. The determination ofthe used resource allocation table may be pre-defined and/or defined inRRC configuration. The indexed row of the resource allocation table maydefine the slot offset K2, the start and length indicator SLIV, ordirectly the start symbol S and the allocation length L, the PUSCHmapping type, and the number of repetitions (if RRC parameternumberOfRepetitions is present in the resource allocation table) to beapplied in the PUSCH transmission. It is noted that RRC parameter is akind of high-layer parameter.

For PUSCH scheduled by DCI format 0_1, if RRC parameterpusch-RepTypeIndicatorDCI-0-1 is set to ‘pusch-RepTypeB’, the UE mayapply PUSCH repetition Type B procedure when determining the time domainresource allocation. For PUSCH scheduled by DCI format 0_2, if RRCparameter pusch-RepTypeIndicatorDCI-0-2 is set to ‘pusch-RepTypeB’, theUE may apply PUSCH repetition Type B procedure when determining the timedomain resource allocation. Otherwise, the UE may apply PUSCH repetitionType A procedure when determining the time domain resource allocationfor PUSCH scheduled by PDCCH.

For PUSCH repetition Type A, the starting symbol S relative to the startof the slot, and the number of consecutive symbols L counting from thesymbol S allocated for the PUSCH may be determined from the start andlength indicator SLIV of the indexed row: if (L−1)≤7 thenSLIV=14(L−1)+S, otherwise SLIV=14(14−L+1+(14−1−S), where 0<L≤14−S.

For PUSCH repetition Type A, when transmitting PUSCH scheduled by DCIformat 0_1 or 0_2 in PDCCH with CRC scrambled with C-RNTI, MCS-C-RNTI,or CS-RNTI with NDI=1, the number of repetitions K may be determined as:if RRC parameter numberOfRepetitions is present in the resourceallocation table, the number of repetitions K may be equal tonumberOfRepetitions; else if the UE is configured with RRC parameterpusch-AggregationFactor, the number of repetitions K may be equal topusch-AggregationFactor; otherwise K=1.

For PUSCH repetition Type A, the number of slots used for TBSdetermination N is equal to 1.

If the UE is not capable of a certain coverage enhancement feature(s)(e.g. available slot based PUSCH repetition counting) or if the UE isnot provided with a certain coverage enhancement configuration(s) (e.g.available slot based PUSCH repetition counting), the following may beapplied. For PUSCH repetition Type A, in case K>1, the same symbolallocation may be applied across the K consecutive slots and the PUSCHmay be limited to a single transmission layer. The UE may repeat the TBacross the K consecutive slots applying the same symbol allocation ineach slot. The redundancy version to be applied on the nth transmissionoccasion of the TB, where n=0, 1, . . . K−1, may be determined asdescribe below. For PUSCH repetition Type A, a PUSCH transmission in aslot of a multi-slot PUSCH transmission may be omitted according to theconditions at least and/or at most in, PUSCH-priority based procedure,slot configuration based procedure, slot format based procedure andcancellation indication based procedure. For example, a slot may bedetermined as available if the slot is available according to all theconditions defined in those procedures, and/or the slot may bedetermined as not available if the slot is not available according to atleast one of the conditions defined in those procedures. K may be aninteger.

If the UE is capable of a certain coverage enhancement feature(s) and/orif the UE is provided with a certain coverage enhancementconfiguration(s), the following may be applied. For PUSCH repetitionType A, in case K>1, the same symbol allocation may be applied acrossthe K available slots (i.e. the first K slots which are available forthe PUSCH transmission) and the PUSCH may be limited to a singletransmission layer. The UE may repeat the TB across the K consecutiveslots applying the same symbol allocation in each slot. The K availableslots may be determined according to the conditions at least and/or atmost in, PUSCH-priority based procedure, slot configuration basedprocedure, slot format based procedure and cancellation indication basedprocedure. For example, a slot may be determined as available if theslot is available according to all the conditions defined in thoseprocedures, and/or the slot may be determined as not available if theslot is not available according to at least one of the conditionsdefined in those procedures.

If the UE is capable of a certain coverage enhancement feature(s) and/orif the UE is provided with a certain coverage enhancementconfiguration(s), the following may be applied. For PUSCH repetitionType A, in case K>1, the same symbol allocation may be applied acrossthe K available slots (i.e. the first K slots which are available forthe PUSCH transmission) and the PUSCH may be limited to a singletransmission layer. The UE may repeat the TB across the K availableslots applying the same symbol allocation in each slot. The K availableslots may be determined according to the conditions at least and/or atmost in first RRC parameters. The first RRC parameters may be one ormore of tdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated,ssb-PositionsInBurst, numberOfRepetitions,BandCombination-UplinkTxSwitch, repK, repK-RV, pusch-AggregationFactor,nrofSlots, configuredGrantConfig, cg-nrofSlots, cg-nrofPUSCH-InSlot,timeDomainAllocation, numberOfInvalidSymbolsForDL-UL-Switching,invalidSymbolPattern, and periodicityAndPattern. For PUSCH repetitionType A, a PUSCH transmission in a slot of a multi-slot PUSCHtransmission is omitted according to the conditions at least and/or atmost in second RRC parameters. The second RRC parameters may be one ormore of tdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated,ssb-PositionsInBurst, numberOfRepetitions,BandCombination-UplinkTxSwitch, repK, repK-RV, pusch-AggregationFactor,nrofSlots, configuredGrantConfig, cg-nrofSlots, cg-nrofPUSCH-InSlot,timeDomainAllocation, numberOfInvalidSymbolsForDL-UL-Switching,invalidSymbolPattern, and periodicityAndPattern.

The configuredGrantConfig may be referred to the ConfiguredGrantConfig.

The configuredGrantConfig may be referred to as theConfiguredGrantConfig.

When PUSCH resource allocation is semi-statically configured by higherlayer parameter configuredGrantConfig in BWP-UplinkDedicated informationelement, and the PUSCH transmission corresponding to a configured grant,the following higher layer parameters are applied in the transmission.

For Type 1 PUSCH transmissions with a configured grant, the followingparameters are given in configuredGrantConfig unless mentionedotherwise, and For the determination of the PUSCH repetition type, ifthe higher layer parameter pusch-RepTypeIndicator inrrc-ConfiguredUplinkGrant is configured and set to ‘pusch-RepTypeB’,PUSCH repetition Type B is applied. Otherwise, PUSCH repetition Type Ais applied.

The higher layer parameter pusch-RepTypeIndicator indicates whether UEfollows the behavior for PUSCH repetition Type A or the behavior forPUSCH repetition Type B for each Type 1 configured grant configuration.The value pusch-RepTypeA enables the ‘PUSCH repetition Type A’ and thevalue pusch-RepTypeB enables the ‘PUSCH repetition Type B’. The valuepusch-RepTypeB is not configured simultaneously withcg-nrofPUSCH-InSlot-r16 and cg-nrofSlots-r16.

For PUSCH repetition Type A, the selection of the time domain resourceallocation table follows the rules for DCI format 0_0 on UE specificsearch space.

For PUSCH repetition Type A, the selection of the time domain resourceallocation table is as follows. If pusch-RepTypeIndicatorDCI-0-1 inpusch-Config is configured and set to ‘pusch-RepTypeA’,pusch-TimeDomainResourceAllocationListDCI-0-1 in pusch-Config is used.Otherwise, pusch-TimeDomainResourceAllocationListDCI-0-2 in pusch-Configis used. It is not expected that pusch-RepTypeIndicator inrrc-ConfiguredUplinkGrant is configured with ‘pusch-RepTypeA’ when noneof pusch-RepTypeIndicatorDCI-0-1 and pusch-RepTypeIndicatorDCI-0-2 inpusch-Config is set to ‘pusch-RepTypeA’.

For PUSCH repetition Type B, the selection of the time domain resourceallocation table is as follows. If pusch-RepTypeIndicatorDCI-0-1 inpusch-Config is configured and set to ‘pusch-RepTypeB’,pusch-TimeDomainResourceAllocationListDCI-0-1 in pusch-Config is used.Otherwise, pusch-TimeDomainResourceAllocationListDCI-0-2 in pusch-Configis used. It is not expected that pusch-RepTypeIndicator inrrc-ConfiguredUplinkGrant is configured with ‘pusch-RepTypeB’ when noneof pusch-RepTypeIndicatorDCI-0-1 and pusch-RepTypeIndicatorDCI-0-2 inpusch-Config is set to ‘pusch-RepTypeB’.

More details of resource allocation in time domain for PUSCH withconfigured grant is described. For PUSCH transmissions with a Type 1 orType 2 configured grant, the number of (nominal) repetitions K to beapplied to the transmitted transport block may be provided by theindexed row in the time domain resource allocation table ifnumberOfRepetitions is present in the table; otherwise K may be providedby the higher layer configured parameters repK. The UE may not beallowed to transmit anything on the resources configured by RRCparameter configuredGrantConfig if the higher layers did not deliver atransport block to transmit on the resources allocated for uplinktransmission without grant.

A set of allowed periodicities P are defined in RRC configuration. TheRRC parameter cg-nrofSlots, may provide the number of consecutive slotsallocated within a configured grant period. The RRC parametercg-nrofPUSCH-InSlot may provide the number of consecutive PUSCHallocations within a slot, where the first PUSCH allocation may followthe RRC parameter timeDomainAllocation for Type 1 PUSCH transmission orthe higher layer configuration according to MAC procedure, and UL grantreceived on the DCI for Type 2 PUSCH transmissions, and the remainingPUSCH allocations may have the same length and PUSCH mapping type, andmay be appended following the previous allocations without any gaps. Thesame combination of start symbol and length and PUSCH mapping type mayrepeat over the consecutively allocated slots.

The UE may not be expected to be configured with the time duration forthe transmission of K repetitions larger than the time duration derivedby the periodicity P. If the UE determines that, for a transmissionoccasion, the number of symbols available for the PUSCH transmission ina slot is smaller than transmission duration L, the UE may not transmitthe PUSCH in the transmission occasion.

The procedures apply to PUSCH transmissions of PUSCH repetition Type Awith a Type 1 or Type 2 configured grant. The RRC parameter repK-RVdefines the redundancy version pattern to be applied to the repetitions.If cg-RetransmissionTimer is provided, the redundancy version for uplinktransmission with a configured grant is determined by the UE. If theparameter repK-RV is not provided in the configuredGrantConfig andcg-RetransmissionTimer is not provided, the redundancy version foruplink transmissions with a configured grant may have to be set to 0. Ifthe parameter repK-RV is provided in the configuredGrantConfig andcg-RetransmissionTimer is not provided, for the nth transmissionoccasion among K repetitions, n=1, 2, . . . , K, it is associated with(mod(n−1,4)+1)^(th) value in the configured RV sequence. If a configuredgrant configuration is configured with startingFromRV0 set to ‘off’, theinitial transmission of a transport block may only start at the firsttransmission occasion of the K repetitions. Otherwise, the initialtransmission of a transport block may start the first transmissionoccasion of the K repetitions if the configured RV sequence is{0,2,3,1}, any of the transmission occasions of the K repetitions thatare associated with RV=0 if the configured RV sequence is {0,3,0,3},and/or any of the transmission occasions of the K repetitions if theconfigured RV sequence is {0,0,0,0}, except the last transmissionoccasion when K≥8.

If a configured grant configuration is not configured withstartingFromRV0 set to ‘off’ and if available slot-based counting isconfigured, the initial transmission of a transport block may start atthe first transmission occasion of the K repetitions.

If a configured grant configuration is not configured withstartingFromRV0 set to ‘off’ and if available slot-based counting is notconfigured, the initial transmission of a transport block may start thefirst transmission occasion of the K repetitions if the configured RVsequence is {0,2,3,1}, any of the transmission occasions of the Krepetitions that are associated with RV=0 if the configured RV sequenceis {0,3,0,3}, and/or any of the transmission occasions of the Krepetitions if the configured RV sequence is {0,0,0,0}, except the lasttransmission occasion when K≥8.

If a configured grant configuration is not configured withstartingFromRV0 set to ‘off’ and if available slot-based counting isconfigured, the initial transmission of a transport block may start thefirst transmission occasion of the K repetitions if the configured RVsequence is {0,2,3,1}, any of the transmission occasions of the Krepetitions that are associated with RV=0 if the configured RV sequenceis {0,3,0,3}, and/or any of the transmission occasions of the Krepetitions if the configured RV sequence is {0,0,0,0}, except the lasttransmission occasion when K≥8.

If a configured grant configuration is not configured withstartingFromRV0 set to ‘off’ and if available slot-based counting is notconfigured, the initial transmission of a transport block may start thefirst transmission occasion of the K repetitions if the configured RVsequence is {0,2,3,1}, any of the transmission occasions of the Krepetitions that are associated with RV=0 assuming the transmissionoccasions of the K repetitions are determined based on consecutivephysical slots if the configured RV sequence is {0,3,0,3}, and/or any ofthe transmission occasions of the K repetitions if the configured RVsequence is {0,0,0,0}, except the last transmission occasion when K≥8.

For any RV sequence, the repetitions may have to be terminated aftertransmitting K repetitions, or at the last transmission occasion amongthe K repetitions within the period P, or from the starting symbol ofthe repetition that overlaps with a PUSCH with the same HARQ processscheduled by DCI format 0_0, 0_1 or 0_2, whichever is reached first. Inaddition, the UE may have to terminate the repetition of a transportblock in a PUSCH transmission if the UE receives a DCI format 0_1 withDFI flag provided and set to ‘1’, and if in this DCI the UE detects ACKfor the HARQ process corresponding to that transport block.

The UE is not expected to be configured with the time duration for thetransmission of K repetitions larger than the time duration derived bythe periodicity P. If the UE determines that, for a transmissionoccasion, the number of symbols available for the PUSCH transmission ina slot is smaller than transmission duration L, the UE does not transmitthe PUSCH in the transmission occasion.

For unpaired spectrum and if the UE is not providedSSB-MTCAdditionalPCI, when an RRC parameter AvailableSlotCounting isenabled and K>1, the UE determines N*K slots for a PUSCH transmission ofa PUSCH repetition Type A, based on RRC parameterstdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated andssb-PositionsInBurst. A slot is not counted in the number of N*K slotsfor PUSCH transmission of a PUSCH repetition Type A if at least one ofthe symbols indicated by the indexed row of the used resource allocationtable in the slot overlaps with a DL symbol indicated bytdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated ifprovided, or a symbol for reception of an SS/PBCH block with indexprovided by ssb-PositionsInBurst in SIB1 or by ssb-PositionsInBurst inServingCellConfigCommon. Otherwise, the UE determines N*K consecutiveslots for a PUSCH transmission of a PUSCH repetition Type A.

For unpaired spectrum and if the UE not provided SSB-MTCAdditionalPCI,there may be several options.

In the first option, when an RRC parameter AvailableSlotCounting isenabled and K>1, the UE determines N*K slots (i.e. N*K available slots)for a PUSCH transmission of a PUSCH repetition Type A, based on RRCparameters tdd-UL-DL-ConfigurationCommon,tdd-UL-DL-ConfigurationDedicated and ssb-PositionsInBurst (i.e. theavailable slot counting is used). With the available slot counting, aslot can be basically counted as an available slot for PUSCHtransmission of a PUSCH repetition Type A. A slot is not counted in thenumber of N*K slots (i.e. the slot is determined as not an availableslot) for PUSCH transmission of a PUSCH repetition Type A if at leastone of the symbols indicated by the indexed row of the used resourceallocation table in the slot overlaps with a DL symbol indicated bytdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated ifprovided, or a symbol for reception of an SS/PBCH block with indexprovided by ssb-PositionsInBurst in SIB1 or by ssb-PositionsInBurst inServingCellConfigCommon, or a symbol for reception of an SS/PBCH blockwith index provided by ssb-PositionsInBurst in any ofSSB-MTCAdditionalPCI(s) associated to physical cell ID(s) with activeTCI states with or without the condition that if the UE is providedSSB-MTCAdditionalPCI and/or is not provided DLorJoint-TCIState orfollowUnifiedTCIstate. Otherwise (i.e. when an RRC parameterAvailableSlotCounting is not enabled or when K=1), the UE determines N*Kconsecutive slots (i.e. N*K physical slots) for a PUSCH transmission ofa PUSCH repetition Type A (i.e. the physical slot counting is used). TheUE may not expect that RRC parameter AvailableSlotCounting set toenabled is provided together with more than X SSB-MTCAdditionalPCIconfigurations, where X is a positive integer within a range of greaterthan or equal to 1 and smaller than 16 (e.g. a small integer such as 1,2, 3, or 4). X may be a pre-determined number. X may be a fixed number.

It is noted that the UE may be able to be provided at most 16SSB-MTCAdditionalPCI configurations (also referred to as RRC parameters:the first SSB-MTCAdditionalPCI, the second SSB-MTCAdditionalPCI, . . .the sixteenth SSB-MTCAdditionalPCI) where each RRC parameterSSB-MTCAdditionalPCI may be used by the gNB to provide the UE anadditional physical cell ID (PCI) which is different from serving cell'sPCI. The additional PCI may be corresponding to neighbor cell whichparticipates inter-cell multiple-TRP operation (transmission/reception)to/from the UE in the serving cell. In other words, each of theSSB-MTCAdditionalPCI may indicate an additional PCI or may indicateassociation of SSB with the cell having different PCI than the servingcell. RRC parameter SSB-MTCAdditionalPCI may include the RRC parameterssb-PositionsInBurst. The RRC parameter ssb-PositionsInBurst may be alsoincluded in RRC parameter SIB1 and in RRC parameterServingCellConfigCommon. The RRC parameter ssb-PositionsInBurst mayindicate the position of SSB in time domain. RRC parameterSSB-MTCAdditionalPCI may be included in RRC configurations for theserving cell.

In the second option, when an RRC parameter AvailableSlotCounting isenabled and K>1 and the number of SSB-MTCAdditionalPCI configurations isless than or equal to X, the UE determines N*K slots for a PUSCHtransmission of a PUSCH repetition Type A, based on RRC parameterstdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated andssb-PositionsInBurst. A slot is not counted in the number of N*K slotsfor PUSCH transmission of a PUSCH repetition Type A if at least one ofthe symbols indicated by the indexed row of the used resource allocationtable in the slot overlaps with a DL symbol indicated bytdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated ifprovided, or a symbol for reception of an SS/PBCH block with indexprovided by ssb-PositionsInBurst in SIB1 or by ssb-PositionsInBurst inServingCellConfigCommon, or a symbol for reception of an SS/PBCH blockwith index provided by ssb-PositionsInBurst in any ofSSB-MTCAdditionalPCI(s) associated to physical cell ID(s) with activeTCI states with or without the condition that if the UE is not providedDLorJoint-TCIState or followUnifiedTCIstate. Otherwise (i.e. when an RRCparameter AvailableSlotCounting is not enabled or when K=1 or when thenumber of SSB-MTCAdditionalPCI configurations greater than X), the UEdetermines N*K consecutive slots for a PUSCH transmission of a PUSCHrepetition Type A. With the second option, whether the available slotcounting or the physical slot counting is used may depends on whetherthe number of SSB-MTCAdditionalPCI configurations exceeds X or not.

In the third option, when an RRC parameter AvailableSlotCounting isenabled and K>1 and the number of SSB-MTCAdditionalPCI configurations ofwhich the associated SSB(s) is in other slot(s) than the slot where theserving cell's SSB is transmitted is less than or equal to X, the UEdetermines N*K slots for a PUSCH transmission of a PUSCH repetition TypeA, based on RRC parameters tdd-UL-DL-ConfigurationCommon,tdd-UL-DL-ConfigurationDedicated and ssb-PositionsInBurst. A slot is notcounted in the number of N*K slots for PUSCH transmission of a PUSCHrepetition Type A if at least one of the symbols indicated by theindexed row of the used resource allocation table in the slot overlapswith a DL symbol indicated by tdd-UL-DL-ConfigurationCommon ortdd-UL-DL-ConfigurationDedicated if provided, or a symbol for receptionof an SS/PBCH block with index provided by ssb-PositionsInBurst in SIB1or by ssb-PositionsInBurst in ServingCellConfigCommon, or a symbol forreception of an SS/PBCH block with index provided byssb-PositionsInBurst in any of SSB-MTCAdditionalPCI(s) associated tophysical cell ID(s) with active TCI states with or without the conditionthat if the UE is not provided DLorJoint-TCIState orfollowUnifiedTCIstate. Otherwise (i.e. when an RRC parameterAvailableSlotCounting is not enabled or when K=1 or when the number ofSSB-MTCAdditionalPCI configurations of which the associated SSB(s) is inother slot(s) than the slot where the serving cell's SSB is transmittedgreater than X), the UE determines N*K consecutive slots for a PUSCHtransmission of a PUSCH repetition Type A. With the third option,whether the available slot counting or the physical slot counting isused may depends on whether the number of SSB-MTCAdditionalPCIconfigurations of which the associated SSB(s) is in other slot(s) thanthe slot where the serving cell's SSB is transmitted exceeds X or not.

In the fourth option, when an RRC parameter AvailableSlotCounting isenabled and K>1, the UE determines N*K slots for a PUSCH transmission ofa PUSCH repetition Type A, based on RRC parameterstdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated andssb-PositionsInBurst. A slot is not counted in the number of N*K slotsfor PUSCH transmission of a PUSCH repetition Type A if at least one ofthe symbols indicated by the indexed row of the used resource allocationtable in the slot overlaps with a DL symbol indicated bytdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated ifprovided, or a symbol for reception of an SS/PBCH block with indexprovided by ssb-PositionsInBurst in SIB1 or by ssb-PositionsInBurst inServingCellConfigCommon, or a symbol for reception of an SS/PBCH blockwith index provided by ssb-PositionsInBurst in any of configuredSSB-MTCAdditionalPCI(s) with or without the condition that if the UE isnot provided DLorJoint-TCIState or followUnifiedTCIstate. Otherwise(i.e. when an RRC parameter AvailableSlotCounting is not enabled or whenK=1), the UE determines N*K consecutive slots for a PUSCH transmissionof a PUSCH repetition Type A. The UE may not expect that RRC parameterAvailableSlotCounting set to enabled is provided together with more thanX SSB-MTCAdditionalPCI configurations.

In the fifth option, when an RRC parameter AvailableSlotCounting isenabled and K>1 and the number of SSB-MTCAdditionalPCI configurations isless than or equal to X, the UE determines N*K slots for a PUSCHtransmission of a PUSCH repetition Type A, based on RRC parameterstdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated andssb-PositionsInBurst. A slot is not counted in the number of N*K slotsfor PUSCH transmission of a PUSCH repetition Type A if at least one ofthe symbols indicated by the indexed row of the used resource allocationtable in the slot overlaps with a DL symbol indicated bytdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated ifprovided, or a symbol for reception of an SS/PBCH block with indexprovided by ssb-PositionsInBurst in SIB1 or by ssb-PositionsInBurst inServingCellConfigCommon, or a symbol for reception of an SS/PBCH blockwith index provided by ssb-PositionsInBurst in any of configuredSSB-MTCAdditionalPCI(s) with or without the condition that if the UE isnot provided DLorJoint-TCIState or followUnifiedTCIstate. Otherwise(i.e. when an RRC parameter AvailableSlotCounting is not enabled or whenK=1 or when the number of SSB-MTCAdditionalPCI configurations greaterthan X), the UE determines N*K consecutive slots for a PUSCHtransmission of a PUSCH repetition Type A. With the fifth option,whether the available slot counting or the physical slot counting isused may depends on whether the number of SSB-MTCAdditionalPCIconfigurations exceeds X or not.

In the sixth option, when an RRC parameter AvailableSlotCounting isenabled and K>1 and the number of SSB-MTCAdditionalPCI configurations ofwhich the associated SSB(s) is in other slot(s) than the slot where theserving cell's SSB is transmitted is less than or equal to X, the UEdetermines N*K slots for a PUSCH transmission of a PUSCH repetition TypeA, based on RRC parameters tdd-UL-DL-ConfigurationCommon,tdd-UL-DL-ConfigurationDedicated and ssb-PositionsInBurst. A slot is notcounted in the number of N*K slots for PUSCH transmission of a PUSCHrepetition Type A if at least one of the symbols indicated by theindexed row of the used resource allocation table in the slot overlapswith a DL symbol indicated by tdd-UL-DL-ConfigurationCommon ortdd-UL-DL-ConfigurationDedicated if provided, or a symbol for receptionof an SS/PBCH block with index provided by ssb-PositionsInBurst in SIB1or by ssb-PositionsInBurst in ServingCellConfigCommon, or a symbol forreception of an SS/PBCH block with index provided byssb-PositionsInBurst in any of configured SSB-MTCAdditionalPCI(s) withor without the condition that if the UE is not providedDLorJoint-TCIState or followUnifiedTCIstate. Otherwise (i.e. when an RRCparameter AvailableSlotCounting is not enabled or when K=1 or when thenumber of SSB-MTCAdditionalPCI configurations of which the associatedSSB(s) is in other slot(s) than the slot where the serving cell's SSB istransmitted greater than X), the UE determines N*K consecutive slots fora PUSCH transmission of a PUSCH repetition Type A. With the sixthoption, whether the available slot counting or the physical slotcounting is used may depends on whether the number ofSSB-MTCAdditionalPCI configurations of which the associated SSB(s) is inother slot(s) than the slot where the serving cell's SSB is transmittedexceeds X or not.

In the seventh option, when an RRC parameter AvailableSlotCounting isenabled and K>1 and the number of SSB-MTCAdditionalPCI configurations isless than or equal to X, the UE determines N*K slots for a PUSCHtransmission of a PUSCH repetition Type A, based on RRC parameterstdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated andssb-PositionsInBurst. A slot is not counted in the number of N*K slotsfor PUSCH transmission of a PUSCH repetition Type A if at least one ofthe symbols indicated by the indexed row of the used resource allocationtable in the slot overlaps with a DL symbol indicated bytdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated ifprovided, or a symbol for reception of an SS/PBCH block with indexprovided by ssb-PositionsInBurst in SIB1 or by ssb-PositionsInBurst inServingCellConfigCommon, or a symbol for reception of an SS/PBCH blockwith index provided by ssb-PositionsInBurst in any of configuredSSB-MTCAdditionalPCI(s) with or without the condition that if the UE isprovided SSB-MTCAdditionalPCI and/or is not provided DLorJoint-TCIStateor followUnifiedTCIstate. When an RRC parameter AvailableSlotCounting isenabled and K>1 and the number of SSB-MTCAdditionalPCI configurations isgreater than X, the UE determines N*K slots for a PUSCH transmission ofa PUSCH repetition Type A, based on RRC parameterstdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated andssb-PositionsInBurst. A slot is not counted in the number of N*K slotsfor PUSCH transmission of a PUSCH repetition Type A if at least one ofthe symbols indicated by the indexed row of the used resource allocationtable in the slot overlaps with a DL symbol indicated bytdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated ifprovided, or a symbol for reception of an SS/PBCH block with indexprovided by ssb-PositionsInBurst in SIB1 or by ssb-PositionsInBurst inServingCellConfigCommon, or a symbol for reception of an SS/PBCH blockwith index provided by ssb-PositionsInBurst in SSB-MTCAdditionalPCIassociated to physical cell ID with active TCI states with or withoutthe condition that if the UE is not provided DLorJoint-TCIState orfollowUnifiedTCIstate. Otherwise (i.e. when an RRC parameterAvailableSlotCounting is not enabled or when K=1), the UE determines N*Kconsecutive slots for a PUSCH transmission of a PUSCH repetition Type A.With the seventh option, whether the any of the configuredSSB-MTCAdditionalPCI(s) or only SSB-MTCAdditionalPCI(s) associated tophysical cell ID(s) with active TCI states is used may depends onwhether the number of SSB-MTCAdditionalPCI configurations exceeds X ornot.

In the eighth option, when an RRC parameter AvailableSlotCounting isenabled and K>1 and the number of SSB-MTCAdditionalPCI configurations ofwhich the associated SSB(s) is in other slot(s) than the slot where theserving cell's SSB is transmitted is less than or equal to X, the UEdetermines N*K slots for a PUSCH transmission of a PUSCH repetition TypeA, based on RRC parameters tdd-UL-DL-ConfigurationCommon,tdd-UL-DL-ConfigurationDedicated and ssb-PositionsInBurst. A slot is notcounted in the number of N*K slots for PUSCH transmission of a PUSCHrepetition Type A if at least one of the symbols indicated by theindexed row of the used resource allocation table in the slot overlapswith a DL symbol indicated by tdd-UL-DL-ConfigurationCommon ortdd-UL-DL-ConfigurationDedicated if provided, or a symbol for receptionof an SS/PBCH block with index provided by ssb-PositionsInBurst in SIB1or by ssb-PositionsInBurst in ServingCellConfigCommon, or a symbol forreception of an SS/PBCH block with index provided byssb-PositionsInBurst in any of configured SSB-MTCAdditionalPCI(s) withor without the condition that if the UE is provided SSB-MTCAdditionalPCIand/or is not provided DLorJoint-TCIState or followUnifiedTCIstate. Whenan RRC parameter AvailableSlotCounting is enabled and K>1 and the numberof SSB-MTCAdditionalPCI configurations of which the associated SSB(s) isin other slot(s) than the slot where the serving cell's SSB istransmitted is greater than X, the UE determines N*K slots for a PUSCHtransmission of a PUSCH repetition Type A, based on RRC parameterstdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated andssb-PositionsInBurst. A slot is not counted in the number of N*K slotsfor PUSCH transmission of a PUSCH repetition Type A if at least one ofthe symbols indicated by the indexed row of the used resource allocationtable in the slot overlaps with a DL symbol indicated bytdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated ifprovided, or a symbol for reception of an SS/PBCH block with indexprovided by ssb-PositionsInBurst in SIB1 or by ssb-PositionsInBurst inServingCellConfigCommon, or a symbol for reception of an SS/PBCH blockwith index provided by ssb-PositionsInBurst in SSB-MTCAdditionalPCIassociated to physical cell ID with active TCI states with or withoutthe condition that if the UE is not provided DLorJoint-TCIState orfollowUnifiedTCIstate. Otherwise (i.e. when an RRC parameterAvailableSlotCounting is not enabled or when K=1), the UE determines N*Kconsecutive slots for a PUSCH transmission of a PUSCH repetition Type A.With the seventh option, whether the any of the configuredSSB-MTCAdditionalPCI(s) or only SSB-MTCAdditionalPCI(s) associated tophysical cell ID(s) with active TCI states is used may depends onwhether the number of SSB-MTCAdditionalPCI configurations of which theassociated SSB(s) is in other slot(s) than the slot where the servingcell's SSB is transmitted exceeds X (i.e. is greater than X) or not(i.e. is less than or equal to X).

For paired spectrum and SUL band, The UE determines N*K consecutiveslots for a PUSCH transmission of a PUSCH repetition type A,irrespective of whether AvailableSlotCounting is enabled or not. For thecase of reduced capability half-duplex UE, and whenAvailableSlotCounting is enabled, a slot is not counted in the number ofN*K slots for a PUSCH transmission of a PUSCH repetition Type A, if atleast one of the symbols indicated by the indexed row of the usedresource allocation table in the slot overlaps with a symbol of anSS/PBCH block with index provided by ssb-PositionsInBurst. Forinter-cell multiple-TRP operation, the afore-mentioned options (i.e. thefirst option to the eighth option) may be applicable.

For both Type 1 and Type 2 PUSCH transmissions with a configured grant,when K>1, for unpaired spectrum, if an RRC parameterAvailableSlotCounting is enabled, the UE may have to repeat the TBacross the N*K slots determined for the PUSCH transmission applying thesame symbol allocation in each slot. Otherwise, the UE may have torepeat the TB across the N*K consecutive slots applying the same symbolallocation in each slot, except if the UE is provided with higher layerparameters cg-nrofSlots and cg-nrofPUSCH-InSlot, in which case the UErepeats the TB in the repK earliest consecutive transmission occasioncandidates within the same configuration. For inter-cell multiple-TRPoperation, the afore-mentioned options (i.e. the first option to theeighth option) may be applicable.

For both Type 1 and Type 2 PUSCH transmissions with a configured grant,when K>1, for paired spectrum, irrespective of whetherAvailableSlotCounting is enabled or not, the UE may have to repeat theTB across the N*K consecutive slots applying the same symbol allocationin each slot, except if the UE is provided with higher layer parameterscg-nrofSlots and cg-nrofPUSCH-InSlot, in which case the UE repeats theTB in the repK earliest consecutive transmission occasion candidateswithin the same configuration. A Type 1 or Type 2 PUSCH transmissionwith a configured grant in a slot is omitted according to the conditionsin the UE procedure(s) for reporting control information, the UEprocedure(s) for determining slot configuration(s) and the UEprocedure(s) associated with cancellation indication.

If the available slot based counting is not configured [or for pairedspectrum], for both Type 1 and Type 2 PUSCH transmissions with aconfigured grant, when K>1, the UE may have to repeat the TB across theK consecutive slots applying the same symbol allocation in each slot,except if the UE is provided with higher layer parameters cg-nrofSlotsand cg-nrofPUSCH-InSlot, in which case the UE repeats the TB in the repKearliest consecutive transmission occasion candidates within the sameconfiguration.

If the available slot based counting is configured [and for unpairedspectrum], for both Type 1 and Type 2 PUSCH transmissions with aconfigured grant, when K>1, the UE may have to repeat the TB across thefirst K available slots applying the same symbol allocation in each slotwhere each of the available slots is a slot having an UL symbol, asdescribed in the UE procedure(s) for determining slot configuration(s),or flexible symbol, as described in the UE procedure(s) for determiningslot configuration(s), that is not SS/PBCH block symbol, for the PUSCH,and[/or] consecutive UL symbols, as described in the UE procedure(s) fordetermining slot configuration(s), or flexible symbols, as described inthe UE procedure(s) for determining slot configuration(s), that are notSS/PBCH block symbols, starting from the first symbol, equal to orlarger than a number of symbols for the PUSCH, except if the UE isprovided with higher layer parameters cg-nrofSlots andcg-nrofPUSCH-InSlot, in which case the UE repeats the TB in the repKearliest consecutive transmission occasion candidates within the sameconfiguration. A Type 1 or Type 2 PUSCH transmission with a configuredgrant in a slot is omitted according to the conditions in the UEprocedure(s) for reporting control information, the UE procedure(s) fordetermining slot configuration(s) and the UE procedure(s) associatedwith cancellation indication. A SS/PBCH block symbol is a symbol of anSS/PBCH block with candidate SS/PBCH block index corresponding to theSS/PBCH block index indicated to a UE by ssb-PositionsInBurst in SIB1 orssb-PositionsInBurst in ServingCellConfigCommon, as described in the UEsynchronization procedure for searching a cell. For inter-cellmultiple-TRP operation, the afore-mentioned options (i.e. the firstoption to the eighth option) may be applicable.

If available slot based counting is not configured [or for pairedspectrum], for both Type 1 and Type 2 PUSCH transmissions with aconfigured grant, when K>1, the UE may have to repeat the TB across theK consecutive slots applying the same symbol allocation in each slot,except if the UE is provided with higher layer parameters cg-nrofSlotsand cg-nrofPUSCH-InSlot, in which case the UE repeats the TB in the repKearliest consecutive transmission occasion candidates within the sameconfiguration.

If available slot based counting is configured [and for unpairedspectrum], for both Type 1 and Type 2 PUSCH transmissions with aconfigured grant, when K>1, the UE may have to repeat the TB across aninitial slot and the following K−1 available slots applying the samesymbol allocation in each slot where the initial slot is a slot havingthe symbol defined in the uplink transmission procedure(s) withoutdynamic grant by the MAC entity and each of the available slots is aslot having an UL symbol, as described in the UE procedure(s) fordetermining slot configuration(s), or flexible symbol, as described inthe UE procedure(s) for determining slot configuration(s), that is notSS/PBCH block symbol, for the PUSCH, and/or consecutive UL symbols, asdescribed in the UE procedure(s) for determining slot configuration(s),or flexible symbols, as described in the UE procedure(s) for determiningslot configuration(s), that are not SS/PBCH block symbols, starting fromthe first symbol, equal to or larger than a number of symbols for thePUSCH, except if the UE is provided with higher layer parameterscg-nrofSlots and cg-nrofPUSCH-InSlot, in which case the UE repeats theTB in the repK earliest consecutive transmission occasion candidateswithin the same configuration. A Type 1 or Type 2 PUSCH transmissionwith a configured grant in a slot is omitted according to the conditionsin the UE procedure(s) for reporting control information, the UEprocedure(s) for determining slot configuration(s) and the UEprocedure(s) associated with cancellation indication. Irrespective ofwhether it is inter-cell multiple-TRP operation or not, a SS/PBCH blocksymbol may be a symbol of an SS/PBCH block with candidate SS/PBCH blockindex corresponding to the SS/PBCH block index indicated to a UE byssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst inServingCellConfigCommon, as described in the UE synchronizationprocedure for searching a cell. Alternatively and/or additionally, forinter-cell multiple-TRP operation (i.e. when at lease oneSSB-MTCAdditionalPCI is provided from the gNB to UE via RRCconfiguration), a SS/PBCH block symbol may be a symbol of an SS/PBCHblock with candidate SS/PBCH block index corresponding to the SS/PBCHblock index indicated to a UE by ssb-PositionsInBurst inMTCAdditionalPCI associated to physical cell ID(s) with active TCIstate(s).

The MAC entity may be included in the medium access control layerprocessing unit 15.

The pusch-Config may be referred to the PUSCH-Config.

The pusch-Config may be referred to as the PUSCH-Config.

If the UE is not capable of a certain coverage enhancement feature(s)(e.g. available slot based PUSCH repetition counting) or if the UE isnot provided with a certain coverage enhancement configuration(s) (e.g.available slot based PUSCH repetition counting), the following (i.e. thenumber of repetitions counted based on contiguous (or continuous, orconsecutive) slots) may be applied. Alternatively or additionally, ifthe UE is capable of a certain coverage enhancement feature(s) and ifthe UE is provided with a slot-counting type configuration (the RRCconfiguration or RRC parameter for indicating whether the number ofrepetitions are counted based on contiguous (or continuous) slots orbased on available slots) which indicates the PUSCH repetition to becounted based on contiguous slots, the following may be applied. Forboth Type 1 and Type 2 PUSCH transmissions with a configured grant, whenK>1, the UE may repeat the TB across the K consecutive slots applyingthe same symbol allocation in each slot, except if the UE is providedwith RRC parameters cg-nrofSlots and cg-nrofPUSCH-InSlot, in which casethe UE may repeat the TB in the repK earliest consecutive transmissionoccasion candidates within the same configuration. A Type 1 or Type 2PUSCH transmission with a configured grant in a slot may be omittedaccording to the conditions at least and/or at most in, PUSCH-prioritybased procedure, slot configuration based procedure, slot format basedprocedure and cancellation indication based procedure. For example, aslot may be determined as available if the slot is available accordingto all the conditions defined in those procedures, and/or the slot maybe determined as not available if the slot is not available according toat least one of the conditions defined in those procedures.

It is noted that the aforementioned slot-counting type configuration maybe referred to as a different name. The existence of the slot-countingtype configuration in RRC configuration message may mean that the numberof repetitions is counted based on available slots while the absence ofthe slot-counting type configuration in RRC configuration message maymean that the number of repetitions is counted based on contiguousslots. Additionally and/or alternatively, the slot-counting typeconfiguration set to the first value (e.g. ‘contiguous’) may mean thatthe number of repetitions is counted based on contiguous slots while theslot-counting type configuration set to the second value (e.g.‘available’) may mean that the number of repetitions is counted based onavailable slots.

For PUSCH repetition Type A, the PUSCH mapping type is set to Type A orType B as defined in Precoding and mapping to physical resources asgiven by the indexed row.

For PUSCH repetition Type B, the PUSCH mapping type is set to Type B.

For PUSCH repetition Type A, when transmitting PUSCH scheduled by DCIformat 0_1 or 0_2 in PDCCH with CRC scrambled with C-RNTI, MCS-C-RNTI,or CS-RNTI with NDI=1, the number of repetitions K is determined as thenumber of repetitions K is equal to numberOfRepetitions ifnumberOfRepetitions is present in the resource allocation table, thenumber of repetitions K is equal to pusch-AggregationFactor elseif theUE is configured with pusch-AggregationFactor, otherwise K=1. The numberof slots used for TBS determination N is equal to 1.

As explained above, there are two counting methods to determines themultiple slots which are used for PUSCH transmission at the UE side andPUSCH reception at the gNB side, one is the available slot counting(also referred to as the counting based on available slots) and theother is the physical slot counting (also referred to as the countingbased on consecutive slots, consecutive-slot counting orregular/normal/legacy counting). In the available-slot counting, the N*Kearliest available slots no earlier than the slot which is determined bythe slot offset K2 may be determined as the slots for a PUSCHtransmission, where a slot is not counted as the available slot if atleast one of the symbols indicated by the indexed row of the usedresource allocation table (i.e., the symbols indicated by the TDRAfield) in the slot overlaps with a DL symbol indicated bytdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated ifprovided, or a symbol of an SS/PBCH block with index provided byssb-PositionsInBurst. In the physical-slot counting, the N*K consecutiveslots starting with the slot which is determined by the slot offset K2may be determined as the slots for a PUSCH transmission, irrespective ofthe overlapping with the DL symbol or the symbol of the SS/PBCH block.Note that the actual transmission in the slot determined for the PUSCHmay or may not be further dropped depending on the collisions with otherchannels and/or signals.

For unpaired spectrum, the UE determines N*K slots for a PUSCHtransmission of TB processing over multiple slots scheduled by DCIformat 0_1 or 0_2, based on tdd-UL-DL-ConfigurationCommon,tdd-UL-DL-ConfigurationDedicated and ssb-PositionsInBurst, and the TDRAinformation field value in the DCI format 0_1 or 0_2. A slot is notcounted in the number of N*K slots for a PUSCH transmission of TBprocessing over multiple slots if at least one of the symbols indicatedby the indexed row of the used resource allocation table in the slotoverlaps with a DL symbol indicated by tdd-UL-DL-ConfigurationCommon ortdd-UL-DL-ConfigurationDedicated if provided, or a symbol of an SS/PBCHblock with index provided by ssb-PositionsInBurst. For inter-cellmultiple-TRP operation, the afore-mentioned options (i.e. the firstoption to the eighth option) may be applicable.

For unpaired spectrum, the UE determines N*K slots for a PUSCHtransmission of a PUSCH repetition Type A scheduled by RAR UL grant,based on tdd-UL-DL-ConfigurationCommon and ssb-PositionsInBurst, and theTDRA information field value in the RAR UL grant. A slot is not countedin the number of N*K slots for a PUSCH transmission of a PUSCHrepetition Type A scheduled by RAR UL grant, if at least one of thesymbols indicated by the indexed row of the used resource allocationtable in the slot overlaps with a DL symbol indicated bytdd-UL-DL-ConfigurationCommon if provided, or a symbol of an SS/PBCHblock with index provided by ssb-PositionsInBurst.

For unpaired spectrum, the ULE determines N*K slots for a PUSCHtransmission of a PUSCH repetition Type A scheduled by DCI format 0_0with CRC scrambled by TC-RNTI, based on tdd-UL-DL-ConfigurationCommonand ssb-PositionsInBurst and the TDRA information field value in the DCIscheduling the PUSCH. A slot is not counted in the number of N*K slotsfor a PUSCH transmission of a PUSCH repetition Type A scheduled by DCIformat 0_0 scrambled by TC-RNTI, if at least one of the symbolsindicated by the indexed row of the used resource allocation table inthe slot overlaps with a DL symbol indicated bytdd-UL-DL-ConfigurationCommon if provided, or a symbol of an SS/PBCHblock with index provided by ssb-PositionsInBurst.

FIG. 9 shows an example of a method for a user equipment (UE). Themethod may comprise acquiring one or more RRC parameters each indicatingan additional physical cell ID (Step S901). The method may also comprisetransmitting a PUSCH in multiple slots (Step S902). The multiple slotsmay be determined by using either an available slot counting method or aphysical slot counting method. Whether the available slot countingmethod or the physical slot counting method is used may depend onwhether the number of the RRC parameters exceed a pre-determined numberor not.

FIG. 10 shows an example of a method for a base station. The method maycomprise sending one or more RRC parameters each indicating anadditional physical cell ID (Step S1001). The method may also comprisereceiving a PUSCH in multiple slots (Step S1002). The multiple slots maybe determined by using either an available slot counting method or aphysical slot counting method. Whether the available slot countingmethod or the physical slot counting method is used may depend onwhether the number of the RRC parameters exceed a pre-determined numberor not.

Each of a program running on the base station device and the terminaldevice according to an aspect of the present invention may be a programthat controls a Central Processing Unit (CPU) and the like, such thatthe program causes a computer to operate in such a manner as to realizethe functions of the above-described embodiment according to the presentinvention. The information handled in these devices is transitorilystored in a Random-Access-Memory (RAM) while being processed.Thereafter, the information is stored in various types ofRead-Only-Memory (ROM) such as a Flash ROM and a Hard-Disk-Drive (HDD),and when necessary, is read by the CPU to be modified or rewritten.

Note that the terminal device 1 and the base station device 3 accordingto the above-described embodiment may be partially achieved by acomputer. In this case, this configuration may be realized by recordinga program for realizing such control functions on a computer-readablerecording medium and causing a computer system to read the programrecorded on the recording medium for execution.

Note that it is assumed that the “computer system” mentioned here refersto a computer system built into the terminal device 1 or the basestation device 3, and the computer system includes an OS and hardwarecomponents such as a peripheral device. Furthermore, the“computer-readable recording medium” refers to a portable medium such asa flexible disk, a magneto-optical disk, a ROM, a CD-ROM, and the like,and a storage device built into the computer system such as a hard disk.

Moreover, the “computer-readable recording medium” may include a mediumthat dynamically retains a program for a short period of time, such as acommunication line that is used to transmit the program over a networksuch as the Internet or over a communication line such as a telephoneline, and may also include a medium that retains a program for a fixedperiod of time, such as a volatile memory within the computer system forfunctioning as a server or a client in such a case. Furthermore, theprogram may be configured to realize some of the functions describedabove, and also may be configured to be capable of realizing thefunctions described above in combination with a program already recordedin the computer system.

Furthermore, the base station device 3 according to the above-describedembodiment may be achieved as an aggregation (an device group) includingmultiple devices. Each of the devices configuring such an device groupmay include some or all of the functions or the functional blocks of thebase station device 3 according to the above-described embodiment. Thedevice group may include each general function or each functional blockof the base station device 3. Furthermore, the terminal device 1according to the above-described embodiment can also communicate withthe base station device as the aggregation.

Furthermore, the base station device 3 according to the above-describedembodiment may serve as an Evolved Universal Terrestrial Radio AccessNetwork (E-UTRAN) and/or NG-RAN (Next Gen RAN, NR-RAN). Furthermore, thebase station device 3 according to the above-described embodiment mayhave some or all of the functions of a node higher than an eNodeB or thegNB.

Furthermore, some or all portions of each of the terminal device 1 andthe base station device 3 according to the above-described embodimentmay be typically achieved as an LSI which is an integrated circuit ormay be achieved as a chip set. The functional blocks of each of theterminal device 1 and the base station device 3 may be individuallyachieved as a chip, or some or all of the functional blocks may beintegrated into a chip. Furthermore, a circuit integration technique isnot limited to the LSI, and may be realized with a dedicated circuit ora general-purpose processor. Furthermore, in a case that with advancesin semiconductor technology, a circuit integration technology with whichan LSI is replaced appears, it is also possible to use an integratedcircuit based on the technology.

Furthermore, according to the above-described embodiment, the terminaldevice has been described as an example of a communication device, butthe present invention is not limited to such a terminal device, and isapplicable to a terminal device or a communication device of afixed-type or a stationary-type electronic device installed indoors oroutdoors, for example, such as an Audio-Video (AV) device, a kitchendevice, a cleaning or washing machine, an air-conditioning device,office equipment, a vending machine, and other household devices.

The embodiments of the present invention have been described in detailabove referring to the drawings, but the specific configuration is notlimited to the embodiments and includes, for example, an amendment to adesign that falls within the scope that does not depart from the gist ofthe present invention. Furthermore, various modifications are possiblewithin the scope of one aspect of the present invention defined byclaims, and embodiments that are made by suitably combining technicalmeans disclosed according to the different embodiments are also includedin the technical scope of the present invention. Furthermore, aconfiguration in which constituent elements, described in the respectiveembodiments and having mutually the same effects, are substituted forone another is also included in the technical scope of the presentinvention.

1. A user equipment (UE) comprising: high-layer processing circuitryconfigured to acquire one or more RRC parameters each indicating anadditional physical cell ID; transmission circuitry configured totransmit a PUSCH in multiple slots, wherein the multiple slots aredetermined by using either an available slot counting method or aphysical slot counting method and whether the available slot countingmethod or the physical slot counting method is used depends on whetherthe number of the RRC parameters exceed a pre-determined number or not.2. A base station comprising: high-layer processing circuitry configuredto send one or more RRC parameters each indicating an additionalphysical cell ID; reception circuitry configured to receive a PUSCH inmultiple slots, wherein the multiple slots are determined by usingeither an available slot counting method or a physical slot countingmethod and whether the available slot counting method or the physicalslot counting method is used depends on whether the number of the RRCparameters exceed a pre-determined number or not.
 3. A method for a userequipment (UE), the method comprising: acquiring one or more RRCparameters each indicating an additional physical cell ID; transmittinga PUSCH in multiple slots, wherein the multiple slots are determined byusing either an available slot counting method or a physical slotcounting method and whether the available slot counting method or thephysical slot counting method is used depends on whether the number ofthe RRC parameters exceed a pre-determined number or not.